Hello,
I am using Authentication Manager 8.2SP3. Today I selected 8 tokens which will shut down soon and chose "assign replacement token" where I chose 8 new tokens. The operation finished but only about half of the new tokens had taken over the PIN of the original token whereas the other half stated "PIN not set". Of course all of the original tokens have a PIN set and all replacement tokens had been assigned in one operation. (The old tokens belong to a batch of test tokens provided by RSA, but that shouldn't matter?).
Bug or feature?
Regards,
Jürgen
Typically pins just migrate, but conflicting policies can cause issues. If a user has an
alphanumeric pin and a software token set up as keyfob style, and it is replaced
with a software token and then that is set up for pinpad style, the alphanumeric pin is now invalid.
Look for any system setting, or token setting, or policy setting, preventing pin from migrating.
Software tokens, hardware tokens, mix ?
Administrator activity report, any evidence ?
System activity report, anything ?