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
Add a Trusted Realm 62Number of Views Error "Unable to resolve trusted user because multiple matching trusted users exist" on RSA Authentication Manager 8.x for… 225Number of Views RSA Authentication Manager 8.X trusted realm sending authentication requests to removed replicas 165Number of Views Unable to add or manage user in RSA Authentication Manager; getting the error: The specified ID is already in use by unre… 5.06KNumber of Views Authentication Manager 8.x Trusted realm logon with user alias fails on RADIUS Client 143Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x