Change How Often the RADIUS Server Updates RADIUS Client Information
By default, RSA Authentication Manager requires up to 600 seconds (10 minutes) to reflect any updates that are made to RADIUS clients that previously authenticated to the RADIUS server. Restarting the RADIUS server causes any changes to take effect immediately.
You can edit the dynamic-clients file to change how often the RADIUS server requests updated information from IPv4 RADIUS clients and from IPv6 RADIUS clients. To apply the same change throughout your deployment, you must edit the file on each primary and replica instance.
Note: Do not make any other changes in the dynamic-clients file. Changes to other configuration values can result in authentication failures for RADIUS clients.
Before you begin
You must have Super Admin and Operations Console administrator credentials.
Procedure
- Log on to the Operations Console on the RSA Authentication Manager primary instance.
- Click Deployment Configuration > RADIUS Servers.
- If prompted, enter the Super Admin User ID and password, and click OK.
- Select the RADIUS server that you want to update, and select Manage Server Files from the context menu.
- On the Manage Server Files page, click the Configuration Files tab.
- Select the dynamic-clients file, and select Edit from the context menu.
- In the configuration section for IPv4 RADIUS clients and in the configuration section for IPv6 RADIUS clients, you can enter new Lifetime values, in seconds. For example, to refresh the clients after 8 minutes, enter:
Lifetime = 480
A value that is too small causes the clients to load too often, but a value that is too large delays the effective time that is required for administration. Enter 0 to never reload client information.
- Click Save & Restart RADIUS Server for the changes to take effect.
After you finish
To copy edits to another RADIUS server in the deployment, select the appropriate RADIUS server from the manage RADIUS Servers page on the primary instance, and copy or make the edits.
Related Articles
Generic REST EDC collector not getting the desired results in entitlement relationship in RSA Governance & Lifecycle 50Number of Views Attempted to read or write protected memory. This is often an indication that other memory is corrupt. 18Number of Views How to access the aveksaServer.log and aveksaServerInfo.log files in RSA Identity Governance & Lifecycle 159Number of Views Radius Client Authentication failed For PIN+Token profile (New PIN Mode) with Cisco Anyconnect VPN 118Number of Views Looping fulfillment workflows cause multiple issues in SecurID Governance & Lifecycle 329Number 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