6.0.3

n
Contains the following Key Usages: Digital Signature, Non Repudiation, Key Encipherment
N The algorithms md2WithRSAEncryption 1.2.840.113549.1.1.2, md5WithRSAEncryption
1.2.840.113549.1.1.4 , and sha1WithRSAEncryption 1.2.840.113549.1.1.5 are not recommended. The algorithm
RSASSA-PSS with OID 1.2.840.113549.1.1.10 is not supported.
VMCA and VMware Core Identity Services
Core identity services are part of every embedded deployment and every platform services node. VMCA is
part of every VMware core identity services group. Use the management CLIs and the vSphere Web Client
to interact with these services.
VMware core identity services include several components.
Table 3‑3. Core Identity Services
Service Description Included in
VMware Directory Service
(vmdir)
Handles SAML certicate management for
authentication in conjunction with vCenter
Single Sign-On.
Platform Services Controller
Embedded deployment
VMware Certicate Authority
(VMCA)
Issues certicates for VMware solution users,
machine certicates for machines on which
services are running, and ESXi host certicates.
VMCA can be used as is, or as an intermediary
certicate authority.
VMCA issues certicates only to clients that can
authenticate to vCenter Single Sign-On in the
same domain.
Platform Services Controller
Embedded deployment
VMware Authentication
Framework Daemon (VMAFD)
Includes the VMware Endpoint Certicate Store
(VECS) and several other authentication services.
VMware administrators interact with VECS; the
other services are used internally.
Platform Services Controller
vCenter Server
Embedded deployment
VMware Endpoint Certificate Store Overview
VMware Endpoint Certicate Store (VECS) serves as a local (client-side) repository for certicates, private
keys, and other certicate information that can be stored in a keystore. You can decide not to use VMCA as
your certicate authority and certicate signer, but you must use VECS to store all vCenter certicates, keys,
and so on. ESXi certicates are stored locally on each host and not in VECS.
VECS runs as part of the VMware Authentication Framework Daemon (VMAFD). VECS runs on every
embedded deployment, Platform Services Controller node, and management node and holds the keystores
that contain the certicates and keys.
VECS polls VMware Directory Service (vmdir) periodically for updates to the TRUSTED_ROOTS store. You
can also explicitly manage certicates and keys in VECS using vecs-cli commands. See “vecs-cli Command
Reference,” on page 125.
VECS includes the following stores.
vSphere Security
72 VMware, Inc.