When you deploy the VMware Cloud Director appliance, it generates self-signed certificates with a validity period of 365 days. If there are expiring or expired certificates in your environment, you can generate new self-signed certificates. You must renew the certificates for each VMware Cloud Director cell individually.
The VMware Cloud Director appliance uses two sets of SSL certificates. The VMware Cloud Director service uses one set of certificates for HTTPS and console proxy communications. The embedded PostgreSQL database and the VMware Cloud Director appliance management user interface share the other set of SSL certificates.
You can change both sets of self-signed certificates. Alternatively, if you use CA-signed certificates for the HTTPS and console proxy communications of VMware Cloud Director, you can change only the embedded PostgreSQL database and appliance management UI certificate. CA-signed certificates include a complete trust chain rooted in a well-known public certificate authority.
Prerequisites
- If you are renewing the certificate for the primary node in a database high availability cluster, place all other nodes in maintenance mode to prevent data loss. See Managing a Cell.
- If FIPS mode is enabled, the root password of the appliance must contain 14 or more characters. See Change the VMware Cloud Director Appliance Root Password.
Procedure
Results
The renewed self-signed certificates are visible in the VMware Cloud Director user interface.
The new PostgreSQL certificate is imported to the VMware Cloud Director truststore on other VMware Cloud Director cells the next time the appliance-sync function runs. The operation can take up to 60 seconds.
What to do next
If necessary, a self-signed certificate can be replaced with a certificate signed by an external or internal certificate authority.