Resynchronize a Token
A token must be resynchronized when the tokencode displayed on the token does not match the tokencode generated by AM. When the tokencodes do not match, authentication attempts fail. Depending on your configuration, users can resynchronize tokens with the Self-Service Console. You can also use the Security Console to resynchronize tokens.
Before you begin
You need access to the tokencodes. The user can read tokencodes to you over the phone.
Procedure
In the Security Console, click Identity > Users > Manage Existing.
Use the search fields to find the user whose token needs to be resynchronized.
Click theAssigned or Unassigned tab.
From the search results, click the user whose token needs to be resynchronized.
From the context menu, click SecurID Tokens.
Click the token that you want to resynchronize.
Click Resynchronize Token.
Enter the tokencode that is displayed on the user's token.
Wait for the tokencode to change, and then enter the new tokencode.
Click Resynchronize.
Related Concepts
Related Articles
The ntpq command gives the error "Request timed out" in RSA Authentication Manager 11Number of Views XudaJurisdictionGetCA() call returns XrcNOTFOUND even though the CA object exists 14Number of Views How DB-Push Works. 29Number of Views Prompt Authenticate Tokencode Users for PINs on Their First Authentication to Cloud Access Service 46Number of Views Set User Expectations for Device Registration and Authentication 176Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…