The original RSA Authenticate app support ends on 31st March 2024, and will then be removed from the app stores. It is now fully superseded by the new RSA Authenticator app
, which also provides your organization with access to new features, such as code matching, and QR Code Authentication.
- If your company does not use
, you can disregard this advisory.
- If you do use
and have not started the migration process, it is time to migrate to RSA's Authenticator V4.3 or later. During the process, you can expect to see one or both of the following logos:
.
Important Notes:
- The “All users” report, available from RSA Cloud Authentication Admin console, lists which application (Authenticate or Authenticator app, and related OS) has been registered for a given user. You can then use this report to identify which users to target for migration.
- Credential Migration is supported when:
- No credentials are present in the Authenticator app
- Only AM-based credentials are present in the Authenticator app and cloud-based credentials are present in the Authenticate app.
- Credential Migration is not supported if the user has cloud-based credentials already present in both the Authenticate app and the Authenticator app.
- We are currently rebranding the RSA Authenticator app from
to
. Once the user completes the credential migration process, they will be presented with the new logo acknowledgment screens.
Steps for Users with Authenticate Application Installed but Have Not yet Installed RSA Authenticator 
:
1. Do not uninstall the RSA Authenticate App .
2. Install RSA Authenticator. Current logo in app stores .
Once installed, RSA Authenticator will detect if the Authenticate app is currently installed and has valid credentials. The Authenticator app will then notify the user to migrate their credentials.
3. Follow the on-screen steps to migrate:
The Authenticate app ’s credentials are migrated to the Authenticator app
and removed from the Authenticate app
.
The Authenticate app registration on My Page is replaced automatically by the Authenticator app registration on the user profile.
Once migration is concluded,
- The user will be taken through the update logo acknowledgment process mentioned above.
- The updated logo
will be used on the device.
- The RSA Authenticator app can be used for all authentication tasks.
- Users can safely remove the Authenticate app
from their device.
Alert: Users can postpone the migration. We advise that you discourage users from doing this. Should they postpone the migration, see the following steps.
Steps for Users with both Authenticate and RSA Authenticator
Installed but have not migrated cloud credentials:
1. Upgrade RSA Authenticator to V 4.3 or later if you have not yet done so.
2. The following screen displays if credential migration is available.
If the user attempts to install new credentials at this point, they will receive the following reminder:
3. To continue with migration, access More.
4. Access Migrate credentials from Authenticate app.
5. Complete the migration process.
Related Articles
How to capture enhanced RSA Authenticator app logs for troubleshooting purposes 258Number of Views Is RSA AA compliant with Federal Act 508 54Number of Views Mandatory Migration/Upgrade Required for RSA Authentication Manager/RSA Authenticate App for iOS and Android/RSA Authentic… 91Number of Views Error: Principal does not possess one or more authenticators when using RSA SecurID Access Authenticate app tokencode with… 555Number of Views RSA Authenticator App Logging 67Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide