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
eLearning Course: RSA Authentication Manager 6.1 to 8.1.x Migration - Part 1 (32:40) 4Number of Views Repair an RSA Trusted Realm 3Number of Views Ping Directory- Identity Source Integration - RSA Ready Implementation Guide 21Number of Views Fully Resynchronize High Availability Tokencodes 79Number of Views IIS Web Agent 7.1.2 has high CPU utilization 161Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide