When replacing an RSA SecurID software token with a new software token the token PIN is not carried over to the new token
Originally Published: 2014-12-02
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1
Platform: Linux
Issue
Resolution
If the RSA SecurID software token has previously been issued to the user as a fob style token (where the user types their PIN into the logon screen of the protected resource and then types the tokencode seen on the iPhone/Android/BlackBerry, etc.) and unassigned then reissued as a replacement token, Authentication Manager would allow the token's original PIN to be carried forward to the replacement token.
If the RSA SecurID software token has not been assigned previously or if it was last issued as a PINPad style (where the user types their PIN into the iPhone/Android/BlackBerry, etc. to generate a passcode that is the PIN embedded into a generated tokencode), it would not carry the PIN forward.
More information on fob style and PINPad style software tokens can be found in the RSA SecurID Software Token Guide for your particular device(s).
Related Articles
"This token pack ID is invalid" error when registering new token pack credentials on Download Central 88Number of Views RSA Authentication Manager services failed to start after activating a new console certificate 583Number of Views How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle 370Number of Views How to install the new RSA ID Plus license 212Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN 605Number 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 RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6
Don't see what you're looking for?