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 Authenticate App Users to Access Resources Protected by RSA Authentication Manager.
Related Articles
Error "Unable to resolve trusted user because multiple matching trusted users exist" on RSA Authentication Manager 8.x for… 227Number of Views RSA Authentication Manager 8.X trusted realm sending authentication requests to removed replicas 170Number of Views Add a Trusted Realm 72Number of Views Authentication Manager 8.x Trusted realm logon with user alias fails on RADIUS Client 144Number of Views Cannot add or manage a user with user ID <UserID>. User IDs must be unique within a deployment. This user ID is already in… 2.07KNumber of Views
Trending Articles
Error on migrating to 7.1.1: IO Error: Connection reset by peer Use shell script to collect hardware and software data for RSA Authentication Manager 8.x Artifacts to gather in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Performance and Scalability Guide RSA Authentication Manager 8.9 Setup and Configuration Guide