How to re-use unassigned tokens via the 'Replace Tokens...' function on Authentication Manager 6.x
Originally Published: 2006-12-21
Article Number
Applies To
Authentication Manager 6.1.x
Microsoft Windows
UNIX
In Authentication Manager 6.x versions, any tokens unassigned from a user will have it last login time and date removed and be treated as a "new " token. Hence, if an administrator uses the "Replace Tokens.." function to replace any expiring tokens and elects not to use new tokens by unchecking "Use New Tokens Only". Hence, it will not be able to distinguish
Issue
Related Articles
Unable to re-edit a RSA Identity Governance & Lifecycle condition containing IN for a rules definition 13Number of Views Access Manager CERTIFICATE authentication fails to re-authenticate after token decryption failed message 92Number of Views RSA Identity Governance & Lifecycle server attempts to apply the patch each time with the message "Patch will be (re-)appl… 36Number of Views AM8.1-Web tier Bootstrap service will not start after re-install 95Number of Views Which signature algorithms are supported when re-signing server certificates? 24Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?