During the installation of HACloud and MSS, self-signed certificates are generated, exchanged, and then used to secure all communication between the session server, web browsers and MSS. Self-signed certificates are identity certificates that are signed by the same entity whose identity they certify.
Both session servers and MSS servers use their generated self-signed certificates to identify themselves to remote clients such as web browsers and other session servers and MSS servers. These self-signed certificates and their private keys are stored in their respective keystores.
The MSS Administrative Console help has detailed information on General Security and Certificates. |
To complete secure communication between clients (web browsers, session servers and MSS servers), the clients must trust the generated self-signed certificate. The session server trusts MSS’ certificate during installation and stores it in its truststore. Likewise, during installation MSS retrieves and trust the session server’s certificate and stores it in its truststore.
Default values:
Password - changeit
Keystore type - bcfks (Bouncy Castle FIPS keystore)
Location of self-signed MSS certificate -MSS/server/etc/<computer-name>.cer
Location of self-signed HACloud session server certificate -HACloud/sessionserver/etc/keystore.cer