000018450 - How to make legacy RSA ACE/Agent work with RSA ACE/Server 5.0

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 Number000018450
Applies ToRSA ACE/Server 5.0 (no longer supported as of 8-15-2004)
UNIX (AIX, HP-UX, Solaris)
Microsoft Windows
RSA ACE/Agent for Windows
RSA ACE/Agent for UNIX
IssueHow to make legacy RSA ACE/Agent work with RSA ACE/Server 5.0
When the sdconf.rec from the ace/data is used with a pre-5.0 client (legacy agent), the authentication will fail with an error message stating that it could not initialize ACE/Server communication
Cannot initialize client-server communications
CauseThe legacy RSA ACE/Agent only know how to work with a Master and Slave ACE/Server. With ACE/Server 5.0, there are no Master and Slave ACE/Servers, only Primary and Replica.
ResolutionTo get legacy agents to work with an ACE/Server 5.0, an sdconf.rec with an Acting Master and Slave ACE/Server needs to be generated and used on the earlier clients.

An sdconf.rec that will work with legacy agents can be generated from the Agent Host menu in Database Administration. This can be done in a number of different ways -- on an individual agent host basis, a group of hosts, or all pre-5.0 hosts. The instructions on how to do this can be found in the on-line help of database administration, under Agent Hosts and Activation on Agent Hosts - Add Agent Host & Assign Acting Servers to Multiple Agent Hosts. This generated sdconf.rec needs to be used with the legacy agent.
Legacy Article IDa468