Setting up collectives with third-party certificates
SSL protects communication between controllers and members. Each server in a collective
has its own identity that is composed of its host name, user directory, and server name. Each server
in a collective has two keystores that are named by default serverIdentity.jks
and collectiveTrust.jks. The keystore contains the SSL certificates that are
needed to declare its own identity and securely establish a communication with other members and
controllers within the collective. For an application to establish an HTTPS inbound connection, each
server has two more keystores that are named by default, key.jks and
trust.jks.