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
Edit Emergency Access Code Format Requirements 82Number of Views Configure Emergency Access for Provisioning 30Number of Views Radiant Logic RadiantOne FID 7.3.12 - Identity Source with AM Configuration - SecurID Access Implementation Guide 7Number of Views Emergency Offline Authentication 72Number of Views Cloud Administration Retrieve License Usage API Version 1 41Number 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
Don't see what you're looking for?