23072 - AUTH_FAILED_BAD_PIN_GOOD_TOKENCODE

Document created by RSA Information Design and Development Employee on Jun 13, 2017Last modified by RSA Link Admin on Sep 18, 2020
Version 15Show Document
  • View in full screen mode

Message: Bad PIN ; but good tokencode detected for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

Description: Authentication attempted

Problem: The user who is assigned the token may no longer possess it because the passcodes are being guessed.

Resolve 23072 - AUTH_FAILED_BAD_PIN_GOOD_TOKENCODE

Confirm if the user possesses the assigned token.

Procedure 

  1. In the Security Console, go to the Home page.

  2. Use Quick Search to find the user.

  3. Select the user to whose token you need to verify.

  4. Under Assigned SecurID Tokens, view the token serial number.

  5. Ask the user for the serial number on the back of the token, and verify if it matches the serial number on the Security Console.

 

 

 

 

 

You are here
Table of Contents > Troubleshooting > Common Error Messages > 23072 Auth Failed Bad PIN Good Tokencode

Attachments

    Outcomes