Summary
As advertised in November 2022, SecurID Authenticator 4.2 for iOS and Android apphas been released with a feature allowing RSA Authenticate app
users to seamlessly migrate to this new application.
We strongly encourage clients to migrate, as the Authenticate app is in maintenance, and newest features, such as QR Code authentication, are only added to the Authenticator app.
Details
The migration is not automatic, and is driven from the installation and use of SecurID Authenticator 4.2 app.
- Current RSA Authenticate app users can continue to use it for the time being and can decide when to migrate.
- SecurID Authenticator 4.2 will detect if RSA Authenticate app is already installed with valid credentials and will then propose to the user to migrate its credentials.
- Migration is not possible if the user has cloud-based credentials already present in both the Authenticate app and the Authenticator app. It will be offered if the user has cloud-based credentials present in the Authenticate app and only AM-based credentials present in the Authenticator app.
- Users can postpone the migration, and decide to do this later, from the app option menu.
- As part of the migration:
- The Authenticate app 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 Authenticator app can be used for all authentication tasks previously managed by the Authenticate app.
- Users can safely remove the Authenticate app from their device.
Migration Scenarios
Users with the Authenticate app
installed, and installing the Authenticator app
for the first time
On first launch, the Authenticator app will propose the user to migrate the credentials present in the Authenticate app, as shown in Figure 1.
Figure 1- Data Migration on Installation
If the users decide to migrate the credentials later, they will be able to do it from the ‘More …’ option in the application. See Figure 2.
Figure 2 - Manual Data Migration
Users with both the Authenticate app
and previous version of the Authenticator app
installed.
Once the Authenticator app is upgraded to 4.2, the Home screen will display a notice about the availability of the migration feature. Users can then rely on the flow identified in Figure 2.
Figure 3 - Notice on Migration Feature
If the users try to install in the Authenticator app cloud-based credentials prior to completing the migration, they will be reminded on the migration feature as per Figure 4.
Figure 4 - Migration Prompt on Credential Addition
Important Note: As implicitly mentioned in Figure 4 above, credential migration is not possible if the users have Cloud-based credential installed on the Authenticator Appprior to the migration. However, if the users then decide to remove all Cloud-based credentials from the Authenticator app, they will be able to complete the migration from the flow shown on Figure 2 above.
Related Articles
How to migrate from RSA Authentication Manager hardware appliance or virtual appliance to virtual appliance in another pla… 287Number of Views Advisory for Migrating credentials from RSA SecurID Software Token 4.2.3 to SecurID Authenticator 5.1 for macOS 197Number of Views Radius clients are not listed after migrating from 7.1 to 8.1 158Number of Views 'java.io.FileNotFoundException: aveksa-version.properties' error running migrate.sh in RSA Identity Governance & Lifecycle 165Number of Views Migrating users from one identity source to another in Authentication Manager 19Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle