Configuring SSL communication between the Operations Center and web browsers

During the installation of the Operations Center, a self-signed digital certificate is generated and is then used for web browser sessions. You can optionally use a certificate that is signed by a third-party certificate authority instead of the self-signed certificate.

About this task

The Operations Center always uses the HTTPS protocol to communicate with web browsers. All communication between your browser and the Operations Center is encrypted by using version 1.2 or later of the TLS protocol.

By default, the self-signed certificate is used to create the secure connection between the browser and the Operations Center. Because the certificate is a self-signed certificate, the web browser is unable to verify the identity of the server and displays a warning. Self-signed certificates are commonly used for intranet web sites, where the danger of an intercepted connection and an impersonated server might not be considered a serious threat. You can bypass the browser's security warning and use the self-signed certificate, or you can replace the self-signed certificate with a certificate from a trusted certificate authority (CA).

To use the self-signed certificate, no further configuration is necessary.

To use a certificate that is signed by a CA, you must complete multiple steps.

Procedure

  1. Create a certificate signing request.
  2. Send the certificate signing request to the certificate authority for signing.
  3. Add the certificate to the truststore file of the Operations Center.