Configure the Maximum Lifetime for New Emergency Access Tokencodes
Configure the Maximum Lifetime for New Emergency Access Tokencodes
You can use the auth_manager.admin.eatokencode_expire_days global configuration value to set the maximum number of days that new Emergency Access Tokencodes can remain active. When a user or administrator activates a new Emergency Access Tokencode, they will not be allowed to set the expiration date later than the maximum lifetime you specify.
Procedure
Run the following command and then restart Authentication Manager services:
./rsautil store -a add_config auth_manager.admin.eatokencode_expire_days days_value GLOBAL 501
where days_value is the maximum number of days that new Emergency Access Tokencodes can remain active.
Related Articles
RSA MFA Agent 2.4.3 for Microsoft Windows Release Notes 82Number of Views Devices running Windows 10 or Windows 11 operating system crash on reboot the machine after RSA MFA Agent 2.3.x for Windo… 380Number of Views Email approvals from Outlook desktop result in "reply could not be understood" in RSA Identity Governance & Lifecycle 110Number of Views Error "Key negotiation exchange failed. Server response was CRED_MISMATCH" with RSA Authentication Agent SDK 8.6 for Java 234Number of Views RSA Announces the Release of RSA MFA Agent 2.4.3 for Microsoft Windows 92Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?