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
Increase the maximum length of a reserve password hash for the RSA Authentication Agent 7.x for Windows 224Number of Views Configure Emergency Access for Provisioning 30Number of Views Deployment Considerations for Risk-Based Authentication 14Number of Views Provide RSA Secure Systems Development Lifecycle process and documentation in Web Threat Detection 18Number of Views "ORA-00020: maximum number of processes (500) exceeded" when attempting to connect to the Oracle Database on IGL 42Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA-2026-07: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?