Root Cause Identified for the SecurID 3.0 App Token Import Issue
Originally Published: 2021-07-02
Last Modified: 2023-11-29
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
How to identify the original StealthAudit Console Machine in RSA Identity Governance & Lifecycle 24Number of Views How to identify the source of a workflow email in RSA Identity Governance and Lifecycle 76Number of Views While trying to reimage an error appears. 30Number of Views RSA Governance & Lifecycle Java Code-Based Connector Datasheet Guide 54Number of Views How to install and configure YourKit Java Profiler Client and Remote Agent for using in profiling RSA Identity Governance … 85Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
Don't see what you're looking for?