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
Error: 'No Relying Party configured or enabled that can be identified by principal 'samlrequestcaller'' in RSA Federated I… 5Number of Views Error: 'No Relying Party configured or enabled that can be identified by principal' in RSA Federated Identity Manager (FIM) 5Number of Views RSA Identity Governance and Lifecyle users who do not belong to role can not be identified 37Number of Views Root Cause Analysis Available for SecurID 3.0.0 for iOS Token Import Issue and SecurID 3.0.2 for iOS Beta Announcement 8Number of Views Identifying Custom Attribute column name in RSA Governance & Lifecycle 92Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?