You can use the vSphere Client to replace the default certificates with custom certificates.
You can use the vSphere Client to generate CSRs for each machine, and replace certificates when you receive them from your internal or third-party Certificate Authority (CA). When you submit the CSRs to your internal or third-party CA, the CA returns signed certificates and the root certificate. You can upload both the root certificate and the signed certificates from the vSphere Client.
Generate Certificate Signing Request for Machine SSL Certificate Using the vSphere Client (Custom Certificates)
The machine SSL certificate is used by the reverse proxy service on every vCenter Server node. Each machine must have a machine SSL certificate for secure communication with other services. You can use the vSphere Client to generate a Certificate Signing Request (CSR) for the machine SSL certificate and to replace the certificate once it is ready.
Prerequisites
The certificate must meet the following requirements:
- Key size: 2048 bits (minimum) to 8192 bits (maximum) (PEM encoded). The vSphere Client and API still accept a key size up to 16384 bits when generating the Certificate Signing Request.
- CRT format
- x509 version 3
- SubjectAltName must contain DNS Name=<machine_FQDN>.
- Contains the following Key Usages: Digital Signature, Key Encipherment
Procedure
What to do next
When the Certificate Authority returns the certificate, replace the existing certificate in the certificate store. See Add Custom Certificates Using the vSphere Client.
Add a Trusted Root Certificate to the Certificate Store Using the vSphere Client
If you want to use third-party certificates in your environment, you must add a trusted root certificate to the certificate store. You can do so using the vSphere Client.
Prerequisites
Obtain the custom root certificate from your third-party or in-house certificate authority (CA).
vSphere accepts only valid CA certificates for import. To be valid, a CA certificate must have the CA bit and the keyCertSign bit set in the basic constraint and the key usage X.509 v3 certificate extensions respectively. This implies that the certificate is a CA and its purpose is for certificate signing. See https://www.rfc-editor.org/rfc/rfc5280 for more information.
Ensure that the keyCertSign bit is set for all the certificates in the chain.
Procedure
Add Custom Certificates Using the vSphere Client
You can use the vSphere Client to add custom Machine SSL certificates to the certificate store.
Usually, replacing the machine SSL certificate for each component is sufficient.
Prerequisites
Generate certificate signing requests (CSRs) for each certificate that you want to replace. See Generate Certificate Signing Request for Machine SSL Certificate Using the vSphere Client (Custom Certificates). Place the certificate and private key in a location that the vCenter Server can access.
Procedure
Generate a VMCA Leaf Certificate
You can generate a leaf certificate that is signed by the VMware Certificate Authority (VMCA) for use in your VMware infrastructure.
In addition to VMware Certificate Authority (VMCA) handling all certificate management, it can generate leaf certificates. Leaf certificates are signed by VMCA and are used to identify other VMware resources. VMCA-generated leaf certificates are not stored in VECS. Also, vCenter Server does not track these leaf certificates for expiration.
Prerequisites
Generate a Certificate Signing Request (CSR) on the host in your VMware infrastructure where you want to install the leaf certificate.
Procedure
Results
The generated Leaf and Root certificates are created and downloaded to the specified location.
What to do next
Import the Leaf and Root certificates to the target host in your VMware infrastructure.