Configure the Maximum Lifetime for New Emergency Access Tokencodes
Last Modified: 2026-08-25
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
What maximum number of characters allowed in form control type "Text Area" for use in RSA Identity Governance and Lifecycle 21Number of Views SID: When importing a software token on a Mac getting password prompt. 10Number of Views Protect Resources with Cloud Access Service 14Number of Views Increase the maximum length of a reserve password hash for the RSA Authentication Agent 7.x for Windows 235Number of Views RSA Authentication Manager 8.x services do not start after activating a new console certificate 1.05KNumber of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device The RSA Identity Governance & Lifecycle AD Collector and AD ADC authentication source fail to establish a TLS 1.2 SSL conn…
Don't see what you're looking for?