Configure Access Restrictions for an Existing Agent
Unrestricted agents pass all user authentication requests to RSA Authentication Manager. Restricted agents only pass requests from users that belong to user groups that have been given access to the agent. You configure access restriction in AM.
Procedure
In the Security Console, click Access > Authentication Agents > Manage Existing.
Click the Restricted or Unrestricted tab, depending on whether the agent that you want to search for is restricted or unrestricted.
Use the search fields to find the agent that you want to configure.
Click the agent that you want to configure, and click Edit.
If you want the agent to be restricted and allow access only to users who belong to user groups with access to the agent, click Allow access only to members of user groups who are granted access to this agent.
Click Save.
Related Concepts
Related Articles
Determining an existing RSA Prime version 54Number of Views How to replace an existing token in RSA Authentication Manager 8.x with a specific token and not with the Next Available T… 122Number of Views Update an existing RSA Cloud Authentication Service Integrated Windows Authentication (IWA) Connector Identity Provider SA… 409Number of Views Importing a token via CT-KIP fails indicating that the token already exists 88Number of Views New Archive run cannot be created due to overlapping with existing archives error in RSA Identity Governance & Lifecycle 41Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle