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 Identifying Custom Attribute column name in RSA Governance & Lifecycle 92Number of Views FortiGate Firewall - RADIUS Configuration Using Admin Access UI - RSA Ready Implementation Guide 67Number of Views How to rollback to a previous version in case of virtual application patch failures in RSA Identity Governance & Lifecycle… 65Number of Views RSA Identity Governance and Lifecycle Account Data Collectors treat data as case sensitive regardless of the setting of th… 39Number of Views
Trending Articles
RSA Release Notes for RSA Authentication Manager 8.8 Downloading RSA Authentication Manager license files or RSA Software token seed records AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 RSA Authentication Manager 8.8 Security Configuration Guide
Don't see what you're looking for?