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
Cisco AnyConnect client displays a second login prompt where RSA Authentication Agent 7.2.1 for Windows is installed 63Number of Views How to remove RSA ACE/Server node secret when RADIUS is in use and no RSA ACE/Agent is installed 108Number of Views rsa_mfa_agent_windows_2.1.4_installation_administration_guide.pdf 191Number of Views RSA Announces the Release of RSA MFA Agent 2.4.3 for Microsoft Windows 106Number of Views RSA MFA Agent 2.4.3 for Microsoft Windows Release Notes 91Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?