Add an SecurID Deployment to RSA Authentication Manager as a Trusted Realm
This task is required in certain cases, when you connect RSA Authentication Manager to identity routers in your deployment because you want the Cloud Authentication Service to verify Authenticate Tokencodes when users access agent-protected resources. Perform this task in any of the following situations:
You have RSA Authentication Manager 8.2 SP1 or later and your Cloud users are not in an identity source configured for RSA Authentication Manager or in the internal database.
You have RSA Authentication Manager 8.2.
You configured RSA Authentication Manager 8.4 to accept Authenticate Tokencodes, but when you use the Security Console to search for users who are in identity sources that are not directly connected to AM, the users cannot be found.
For complete instructions, see Enable RSA Authenticator App Users to Access Resources Protected by RSA Authentication Manager.
Related Articles
System Administrator Accounts 50Number of Views Ping Directory- Identity Source Integration - RSA Ready Implementation Guide 17Number of Views View Enabled User Groups on an Unrestricted Agent 10Number of Views SecurID Authenticate Tokencode Integration Issues and Solutions 8Number of Views Fully Resynchronize High Availability Tokencodes 75Number 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