By default, vRealize Operations Manager installs its own TLS/SSL certificate. The included certificate generates security warnings when you connect to the vRealize Operations Manager monitoring page. If you do not want to use the included certificate, you can use your own TLS/SSL certificate.

A custom TLS/SSL certificate must conform to the following requirements. Using a custom certificate is optional and does not affect vRealize Operations Manager features.

The certificate file contains both a valid private key and a valid certificate chain.

The private key is generated by the RSA or the DSA algorithm.

The private key is not encrypted by a pass phrase.

If the certificate is signed by a chain of other certificates, all other certificates must be included in the certificate file that you plan to import

All the certificates and the private key that are included in the certificate file must be PEM-encoded. vRealize Operations Manager does not support DER-encoded certificates and private keys.

All the certificates and the private key that are included in the certificate file must be in the PEM format. vRealize Operations Manager does not support certificates in the PFX, PKCS12, PKCS7, or other formats.