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
ClassNotFoundException: com.aveksa.migration.db.password.ViewPasswordSettingMigrator while installing a patch in RSA Gover… 61Number of Views Listing the contents of the RSA Authentication Manager Java KeyStore (JKS) files 423Number 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 8.5P4 linux webtier shows online-reinstall required 340Number of Views GUI shows initialization error "ORA-04063: package body "AVUSER.UTILITIES_PKG" has errors" after patching to 7.5.2 P07 in … 384Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide