6.0.3

Table Of Contents
Figure 33. External Certificates are Stored Directly in VECS
Unused
VECS
Machine-Cert
VMware vSphere
VMCA
External CA
(Commercial or
Enterprise)
Signed
Hybrid Deployment
You can have VMCA supply some of the certicates, but use custom certicates for other parts of your
infrastructure. For example, because solution user certicates are used only to authenticate to vCenter Single
Sign-On, consider having VMCA provision those certicates. Replace the machine SSL certicates with
custom certicates to secure all SSL trac.
ESXi Certificate Replacement
For ESXi hosts, you can change certicate provisioning behavior from the vSphere Web Client.
VMware Certificate
Authority mode (default)
When you renew certicates from the vSphere Web Client, VMCA issues the
certicates for the hosts. If you changed the VMCA root certicate to include
a certicate chain, the host certicates include the full chain.
Custom Certificate
Authority mode
Allows you to manually update and use certicates that are not signed or
issued by VMCA.
Thumbprint mode
Can be used to retain 5.5 certicates during refresh. Use this mode only
temporarily in debugging situations.
Where vSphere 6.0 Uses Certificates
In vSphere 6.0 and later, the VMware Certicate Authority (VMCA) provisions your environment with
certicates. This includes machine SSL certicates for secure connections, solution user certicates for
authentication to vCenter Single Sign-On, and certicates for ESXi hosts that are added to vCenter Server.
The following certicates are in use.
Table 32. Certificates in vSphere 6.0
Certificate Provisioned by Stored
ESXi certicates VMCA (default) Locally on ESXi host
Machine SSL certicates VMCA (default) VECS
Solution user certicates VMCA (default) VECS
Chapter 3 vSphere Security Certificates
VMware, Inc. 69