Managing client certificates
If your corporate network uses client certificates for authentication, you
need to configure Jive so it
can authenticate properly.
You can use the Admin Console to choose how to handle
client certificates. If you choose a method that allows for storing certificates in Jive, you can also view and manage
them in the Admin Console. Jive
interface accepts PKCS12 encrypted keys, just as your browser does. Uploading a new certificate
and key takes effect immediately, and all the nodes in a cluster share the same
keystore.
Fastpath:
Certificate management strategies
- Select Java as the client certificate strategy if you're planning to use Java's keytool to manage certificates outside Jive using Java system properties. The Client Certificates dialog box then becomes read-only, and you can't upload any certificates. For more information about the Java keytool, refer to the Oracle documentation.
- Select Issuer as the client certificate strategy if you want to select certificates by issuer. You are required to provide the key and the certificate password when you upload your client certificates to the Jive keystore.
- Select Domain as the client certificate strategy if you want to specify the certificates to use for a specific domain. You are required to provide the domain and the certificate password used to access the cert file when you upload your client certificates to the Jive keystore.
Testing certificate validation
If you put a test URL in the box and click Test Connectivity, you get a detailed report on client and server connectivity.