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
XudaJurisdictionGetCA() call returns XrcNOTFOUND even though the CA object exists 15Number of Views The ntpq command gives the error "Request timed out" in RSA Authentication Manager 12Number of Views How DB-Push Works. 38Number of Views Prompt Authenticate Tokencode Users for PINs on Their First Authentication to Cloud Access Service 47Number of Views Set User Expectations for Device Registration and Authentication 194Number of Views
Trending Articles
Troubleshooting Web Tier deployments on Red Hat Enterprise Linux for RSA Authentication Manager 8.1 How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console Installing rsaservmgr scripts [exec] error reading information on service rsaservmgr error when installing RSA Web Tier o… RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide AFX Connectors remain in a Not Deployed state after patching or upgrading RSA Identity Governance & Lifecycle