You can use vSphere Certificate Manager to generate a CSR and sent the CSR to an enterprise or third-party CA for signing. You can then replace the VMCA root certificate with a custom signing certificate and replace all existing certificates with certificates that are signed by the custom CA.

About this task

You run vSphere Certificate Manager on an embedded installation or on an external Platform Services Controller to replace the VMCA root certificate with a custom signing certificate.

Prerequisites

  • Generate the certificate chain.

  • Gather the information that you will need.

    • Password for administrator@vsphere.local.

    • Valid custom certificate for Root (.crt file).

    • Valid custom key for Root (.key file).

Procedure

  1. Start vSphere Certificate Manager on an embedded installation or on an external Platform Services Controller and select option 2.
  2. Select option 2 again to start certificate replacement and respond to the prompts.
    1. Specify the full path to the root certificate when prompted.
    2. If you are replacing certificates for the first time, you are prompted for information to be used for the machine SSL certificate.

      This information includes the required FQDN of the machine and is stored in the certool.cfg file.

  3. If you replace the root certificate on the Platform Services Controller in a multi-node deployment, follow these steps for each vCenter Server node.
    1. Restart services on the vCenter Server node.
    2. Regenerate all certificates on the vCenter Server instance by using options 3 (Replace Machine SSL certificate with VMCA Certificate) and 6 (Replace Solution user certificates with VMCA certificates).

    When you replace the certificates, VMCA signs with the full chain.

What to do next

If you are upgrading from a vSphere 5.x environment, you might have to replace the vCenter Single Sign-On certificate inside vmdir. See Replace the VMware Directory Service Certificate in Mixed Mode Environments.