Root Cause Identified for the SecurID 3.0 App Token Import Issue
Originally Published: 2021-07-02
RSA has identified the root cause of the token import issue that affected a limited number of users who installed the SecurID 3.0 for iOS app from 6/23/2021 to 6/30/2021. RSA is currently testing the fix with selected customers that reported the issue. A root cause analysis (RCA) report will be made available early next week.
The SecurID 3.0 for Android app will remain on hold while RSA continues to assess it for any possible issue as a precautionary measure. None have been identified at this time.
Related Articles
Identifying Custom Attribute column name in RSA Governance & Lifecycle 92Number of Views AM 7.1: Backup with -D options during DR 29Number of Views RSA SecurID Access: Identify Java Authentication API version/build 85Number of Views RSA Identity Governance and Lifecyle users who do not belong to role can not be identified 38Number of Views Back-up failing after running network vulnerability scanner against Authentication Manager 49Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?