000014212 - RSA authentication agent authenticating only to the Authentication Manager 7.1 primary

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014212
Applies ToRSA Authentication Manager 7.1
Appliance 3.0
RSA Windows Agent
IssueThe RSA agent should authenticate to the replica Authentication Manager server if the primary server is down. The RSA agent should display all Available Authentication Servers when checking the Server Status.
RSA agent only authentication to the Authentication Manager 7.1 primary
On the agent, the Server Status only displays the primary server instead of all available Authentication Servers
CauseThe sdconf.rec file does not contain information on the Authentication Manager replica.

To update the list in the configuration File, follow the following steps:

On the primary Authentication Manager 7.1 server: 

1. Login to the Security Console.  Select Access > Authentication Agents > Authentication Manager Contact List > Automatic Rebalance.

2. Click on the Rebalance Option. You should see the primary and replica server(s) listed.

3. Generate a new configuration file.  From the Security Console select Access > Authentication Agents > Generate Configuration File. Generate and download a new sdconf.rec file.

 On the agent machine:

1. Delete the sdstatus.12 file from C:\Windows\System32

2. Place the newly generated sdconf.rec in the directory.

3. Launch the agent and test authentication.

4. Refresh the agent by closing the agent and launching it again.

5. Go to Local > Server Environment > Server Status to see if the replica server(s) are listed.

       You should now be able to authenticate to the replica server


Legacy Article IDa45223