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
RSA Identity Governance and Lifecyle users who do not belong to role can not be identified 37Number of Views RSA SecurID Access: Identify Java Authentication API version/build 85Number of Views Identifying Custom Attribute column name in RSA Governance & Lifecycle 92Number of Views RSA Governance & Lifecycle - Full Backup Script for Hardware Appliances or Software-Bundles with RSA-provided Database 59Number of Views How to identify the original StealthAudit Console Machine in RSA Identity Governance & Lifecycle 24Number of Views
Trending Articles
RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager Upgrade Process
Don't see what you're looking for?