|Applies To||RSA Product Set: SecurID|
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 7.1, 8.1
|Issue||When replacing an RSA SecurID software token with a new software token the token's existing PIN is not carried over to the new token.|
|Resolution||This is functioning as designed, depending on how the initial token was issued to the user.|
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).