RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.6
Immediately after upgrading the replica side to AM8.6, RADIUS authentication on the replica side fails because access_id and access_key are not set in /opt/rsa/am/radius/radius_connector.ini. After the upgrade, wait about 15 minutes and this file will be updated and RADIUS authentication will succeed.
Before updating, radius_connector.ini does not contain the value of access_id and access_key.
auth_manager.radius.rest_service.access_id =
auth_manager.radius.rest_service.access_key =
Need to wait until updating each values as below.
(e.g.)
auth_manager.radius.rest_service.access_id = pbr8k26bzy09004c6m6uh458X104sse19sz02fy1qy54x8f5016z80tctu8zt468
auth_manager.radius.rest_service.access_key = s2u95191eknx7z6b1X2o64s6c1ux0kt57o4h9fez3b83cvw0v67r31m6uc79z3qx
The radius_connector.ini can be recreated after removing the file and restarting service.
Related Articles
Do Web Services need to be enabled if they are not being used in RSA Identity Governance & Lifecycle? Number of Views MFA Agent for Windows v2.3 Upgrade Is Paused by Error "The following applications are using files that need to be updated" Number of Views Does RSA Identity Governance and Lifecycle MAX_STRING_SIZE need to be modified from STANDARD to EXTENDED to accommodate st… Number of Views Need to add HTML to a review email template in IMG/Aveksa Number of Views How to run the RSA AMBA utility without the need of input files? Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) How to factory reset an RSA Authentication Manager 8.x hardware appliance without a factory reset button from the Operatio… Deploying RSA Authenticator 6.2.2 for Windows Using DISM Artifacts to gather in RSA Identity Governance & Lifecycle
