Authentication failed error when attempting to log in to the RSA SecurID Access Cloud Administration Console
Originally Published: 2020-02-24
Article Number
Applies To
RSA Product/Service Type: Cloud
Issue
The following error shows when attempting to log in to the console after using the Forgot Password link:
Authentication failed
Cause
- The user is not in a target population that is configured in the Access Policy that can access the Cloud Administration Console.
- The login attempt matches a Deny Access rule that is configured in the Access Policy. For example, logging in from a country that is denied access, or the user's network is not on the Trusted Network list.
- The login attempt matches an Authenticate rule, but the configured Assurance Level only allows authentication methods that are not available to the administrator's user. For example,
- Approve when the administrator's user does not have a registered RSA Authenticate app device, or
- RSA SecurID when the administrator's user does not have an assigned RSA SecurID token.
Resolution
Related Articles
"BufferOverflowException" when attempting to authenticate to RSA Via Lifecycle and Governance console 102Number of Views RSA Identity Governance & Lifecycle XARecoveryModule generates an XAException when attempting to roll back changes in fail… 279Number of Views ORA-06550 error when attempting to run the Data_Retention_Pkg in RSA Identity Governance & Lifecycle 75Number of Views XML Parsing Error when attempting SP-initiated Single Sign-On with RSA SecurID Cloud Authentication Service 224Number of Views RSA Community displays an "Agent Integration Error" when attempting to log in using Internet Explorer 11 43Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?