To begin with, we have the PingDirectoryProxy Server installation zip file. In this example, we plan to use SSL security, so we also have a keystore certificate database and a pin file that contains the private key password for the keystore. The keystore files are only necessary when using SSL or StartTLS.

In this deployment scenario, the keystore database is assumed to be a Java Keystore (JKS), which can be created by the keytool program. For more information about using the keytool, see the "Security Chapter" in the PingDirectory Server Administration Guide.

The PingDirectoryProxy directory contains the following:
root@proxy-east-01: ls
ExampleKeystore.jks   ExampleTruststore.jks

The ExampleKeystore.jks keystore file contains the private key entry for the server certificate with the alias server-cert. The server certificate, CA, and intermediate signing certificates are all contained in the ExampleTruststore.jks file. The password for ExampleKeystore.jks is defined in clear text in the corresponding pin file, though the name of the file need not match as it does in our example. The private key password in our example is the same as the password defined for the ExampleKeystore.jks keystore.