PingAuthorize

Joining a topology at setup

To join a new PingAuthorize Server to an existing PingDirectory Server topology during setup, provide connection information for one of the PingDirectory Servers to the setup tool using its --existingDSTopology* options. This PingDirectory Server must be running when you execute the setup tool.

The following table lists some common setup options for joining a PingDirectory Server topology. For a complete list of options, run setup --help.

Option Description

--existingDSTopologyHostName

The address of a PingDirectory Server instance in the topology to be joined.

--existingDSTopologyPort

The LDAP / LDAPS port for communication with the PingDirectory Server to retrieve information about the topology.

--existingDSTopologyUseSSL

Indication that the communication with the PingDirectory Server to retrieve information about the topology should be encrypted with SSL.

--existingDSTopologyUseJavaTruststore

The path to a JKS trust store that has the information needed to trust the certificate presented by the PingDirectory Server when using SSL or StartTLS.

--existingDSTopologyUsePkcs12Truststore

The path to a PKCS #12 trust store that has the information needed to trust the certificate presented by the PingDirectory Server when using SSL or StartTLS.

--existingDSTopologyTrustStorePassword

The password needed to access the contents of the JKS or PKCS #12 trust store. A password is typically required when using a PKCS #12 trust store but is optional when using a JKS trust store.

--existingDSTopologyBindDN

The DN of the account to use to authenticate to the PingDirectory Server, such as cn=Directory Manager. This account must have full read and write access to the configuration and to manage the topology.

--existingDSTopologyBindPassword

The password for the account to use to authenticate to the PingDirectory Server.