6.0.3

Table Of Contents
The vCenter Single Sign-On service stores the token signing certicate and its SSL certicate on disk. You
can change the token signing certicate from the vSphere Web Client.
N Do not change any certicate les on disk unless instructed by VMware documentation or
Knowledge Base Articles. Unpredictable behavior might result otherwise.
Some certicates are stored on the lesystem, either temporarily during startup or permanently. Do not
change the certicates on the le system. Use vecs-cli to perform operations on certicates that are stored
in VECS.
Managing Certificate Revocation
If you suspect that one of your certicates has been compromised, replace all existing certicates, including
the VMCA root certicate.
vSphere 6.0 supports replacing certicates but does not enforce certicate revocation for ESXi hosts or for
vCenter Server systems.
Remove revoked certicates from all nodes. If you do not remove revoked certicates, a man-in-the-middle
aack might enable compromise through impersonation with the account's credentials.
Certificate Replacement in Large Deployments
Certicate replacement in deployments that include multiple management nodes and one or more
Platform Services Controller node is similar to replacement in embedded deployments. In both cases, you
can use the vSphere Certicate Management utility or replace certicates manually. Some best practices
guide the replacement process.
Certificate Replacement in High Availability Environments that Include a Load
Balancer
In environments with less than eight vCenter Server systems, VMware typically recommends a single
Platform Services Controller instance and associated vCenter Single Sign-On service. In larger
environments, consider using multiple Platform Services Controller instances, protected by a network load
balancer. The white paper vCenter Server 6.0 Deployment Guide on the VMware website discusses this setup.
Replacement of Machine SSL Certificates in Environments with Multiple
Management Nodes
If your environment includes multiple management nodes and a single Platform Services Controller, you
can replace certicates with the vSphere Certicate Manager utility, or manually with vSphere CLI
commands.
vSphere Certificate
Manager
You run vSphere Certicate Manager on each machine. On management
nodes, you are prompted for the IP address of the
Platform Services Controller. Depending on the task you perform, you are
also prompted for certicate information.
Manual Certificate
Replacement
For manual certicate replacement, you run the certicate replacement
commands on each machine. On management nodes, you must specify the
Platform Services Controller with the --server parameter. See the following
topics for details:
n
“Replace Machine SSL Certicates with VMCA-Signed Certicates,” on
page 94
n
“Replace Machine SSL Certicates (Intermediate CA),” on page 104
vSphere Security
74 VMware, Inc.