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 Protect Resources with Cloud Access Service 14Number of Views RSA Authentication Manager 8.x services do not start after activating a new console certificate 1.05KNumber of Views SID: When importing a software token on a Mac getting password prompt. 10Number of Views Increase the maximum length of a reserve password hash for the RSA Authentication Agent 7.x for Windows 237Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates RSA Authentication Manager Upgrade Process RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities
Don't see what you're looking for?