If you have your own private key and CA-signed certificate files, importing them into your VMware Cloud Director environment provides the highest level of trust for SSL communications and helps you secure the connections within your cloud infrastructure.
If you want to import private keys and CA-signed SSL certificates to VMware Cloud Director 10.4, see Import Private Keys and CA-Signed SSL Certificates to the VMware Cloud Director Appliance 10.4.
Starting with VMware Cloud Director 10.4, both the console proxy traffic and HTTPS communications go over the default 443 port. You do not need a separate certificate for the console proxy.
Prerequisites
-
To verify that this is the relevant procedure for your environment needs, familiarize yourself with SSL Certificate Creation and Management of the VMware Cloud Director Appliance.
- Copy your intermediate certificates, root CA certificate, CA-signed HTTPS service certificate to the appliance.
- Verify that the key and certificate you want to import are a PEM-encoded PKCS #8 private key and a PEM-encoded X.509 certificate.
Procedure
What to do next
- If you are using wildcard certificates, see Deploy the VMware Cloud Director Appliance 10.4.1 and Later with a Signed Wildcard Certificate for HTTPS Communication.
- If you are not using wildcard certificates, repeat this procedure on all VMware Cloud Director appliance cells in the server group.
- For more information on replacing the certificates for the embedded PostgreSQL database and for the VMware Cloud Director appliance management user interface, see Replace a Self-Signed Embedded PostgreSQL and VMware Cloud Director Appliance Management UI Certificate.