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
How to define a custom attribute as a user with group review rights in RSA Identity Governance and Lifecycle 31Number of Views Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service 88Number of Views Listing the contents of the RSA Authentication Manager Java KeyStore (JKS) files 435Number of Views System down with Initialization Status 'ORA-06502: PL/SQL:numeric or value error: raw variable length too long' error afte… 164Number of Views Backup and scan for updates using NFS fails after upgrading to RSA Authentication Manager 8.4 322Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third …