REMINDER: Upcoming RSA Authentication Change - Action Required
RSA is enhancing the authentication experience for the RSA Community, myRSA, the RSA Partner Portal, and the Enrollment Portal during March 2025. You’ll need to take action to ensure that you and your users can continue logging in without interruption. See the following for more information:
What's Changing?
- Security questions and On-Demand Authentication (ODA) will no longer be used for step-up authentication.
- Users will now be required to configure a Multi-Factor Authentication (MFA) authenticator to use for step-up authentication when necessary.
- Supported MFA authenticators include:
- RSA Authenticator app (iOS, Android, Windows, or macOS)
- FIDO security key
- Windows Hello
- Federal Use Case: Federal Resources in a Sensitive Compartmented Information Facility (SCIF)
- If your users are not permitted to use one of the MFA authenticators above to log in, please reach out to your Account Manager for more information on how to maintain access to the services through other secured means.
What You Need to Do
To prevent login disruptions, please set up your MFA authenticator(s) as soon as possible (if you haven't done so already) using the steps below.
- Visit the Authenticator Enrollment Page to configure your MFA authenticator.
- Follow these step-by-step instructions to complete setup.
- If you wish to verify or add multiple authenticators, refer to this article for guidance.
If you experience any issues, please contact RSA Support for assistance.
Thank you for your cooperation as we improve our authentication security and user experience.
Related Articles
ID Plus Plans - Legacy 167Number of Views Remote AFX Server does not start, there is a SocketException in esb.AFX_INIT.log, and OpenSSL cannot complete an SSL Hands… 331Number of Views Upgrade to RSA Authentication Manager 8.4.0 breaks LDAPS and other TLS/SSL connections 812Number of Views Authentication Manager 8.8 update breaks TLS connections; TLS Handshake error no cipher suites in common 72Number of Views PAM Agent is failing to connect to RSA Servers (Curl error code: 35) 37Number of Views
Trending Articles
RSA Governance & Lifecycle Generic RESTful Web Service Connector Application Guide RSA Release Notes: Cloud Access Service and RSA Authenticators RSA Authentication Manager Upgrade Process RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?