Description:
When CA Directory is installed on a server, part of the installation is defining the DXadmind configuraton. This configuration is used not only for the DXadmind own use, but it's also used as an authentication mechanism by DXmanager. This techdoc explains the relationship between DXmanager and DXadmind.
Solution:
The purpose of the DXadmind password is so that a DXmanager connection can be authenticated. The DXadmind password is defined in two different locations, and it is essential that the DXadmind password be the same across the entire DXmanager backbone.
The two places that the DXadmind password is defined are:
It is vital that the DXadmind password is the same no matter how many CA Directory hosts you deploy. Having a consistent password across your entire backbone will ensure that the one DXmanager server will be able to connect to all your Directory hosts.
DXmanager and DXadmind function in a manager (DXmanager) & agent (DXadmind) style relationship.
Periodically DXmanager will connect to each DXadmind process. In order for this connection to be authenticated, DXmanager and DXadmind need to exchange and verify a set of credentials.
This authentication process uses the following high level steps:
<Please see attached file for image>
In order to initially configure the DXadmind password and other required items, the process is:
When you install each directory server the installation will ask for:
So if you were to install 3 directory servers, during the install you would point them all at the same DXmanager trusted host, communicating on TCP port 2123 and all would have the same DXadmind password.
When you install DXmanager and come to configure the "backbone defaults", there is a section in the GUI which allows you to define the DXadmind configuration details.
An illustration of the configuration section is below:
<Please see attached file for image>