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
Delinea - SAML Relying Party Configuration - RSA Ready Implementation Guide 9Number of Views ISAPI filters sdiisflt.dll and sdiischk.dll Status appears as 'Not Loaded' Note: the filter referred to as sdiisflt.dll ac… 9Number of Views Specops Software uReset - SecurID Authentication API with AM Configuration - RSA Ready SecurID Access Implementation Guide 13Number of Views RSA Announces the Release of RSA MFA Agent 2.4.3 for Microsoft Windows 112Number of Views RSA MFA Agent 2.4.3 for Microsoft Windows Release Notes 96Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA Authentication Manager Patch Updates How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?