Replace a Token with the Next Available Token
Occasionally, you must assign a new token to a user. For example, you must assign a new token to a user whose existing token has been permanently lost or destroyed. A user also needs a new token if his or her current token has expired. Use this procedure to replace a token with a specific unassigned token.
Replaced tokens are either unassigned or deleted from the deployment, depending on your configuration.
Instead of replacing an expired software token that was distributed in RSA Authentication Manager 8.2 or later, you can provide a new expiration date and avoid having to provision and distribute the token again. You cannot extend the expiration date if the token is already being replaced. For more information, see Extending Software Token Lifetimes.
Procedure
In the Security Console, click Identity > Users > Manage Existing.
Use the search fields to find the user whose token you want to replace.
From the search results, click the user whose token you want to replace.
From the context menu, click SecurID Tokens.
Click the token that you want to replace.
From the context menu, select Replace with Next Available Token.
Deliver the replacement token to the user. The user may begin using the new token immediately.
Related Concepts
Related Articles
How to replace an existing token in RSA Authentication Manager 8.x with a specific token and not with the Next Available T… 118Number of Views Replace a Token for a User 27Number of Views Delete a Token 25Number of Views New PIN Mode and Next Token Mode fail on Cisco VPN 3000 Concentrator with RSA ACE/Server 42Number of Views Assign a Replacement Token 46Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x