This article explains the interaction that occurs when Virtual Volumes connects to the VMware Certificate Authority (VMCA) that is part of the vSphere 6.0 environment. By default, VMCA generates all internal certificates used in vSphere environment, including certificates for newly added ESXi hosts and VASA Providers that manage or represent storage systems. Storage that supports Virtual Volumes uses a new VASA 2.0 Provider. Communication with the VASA Provider is protected by SSL certificates. These certificates come from the VASA Provider or from VMCA:
- Directly provided by the VASA Provider for long-term use, and is either self-generated and self-signed, or derived from an external Certificate Authority
- Generated by VMCA for use by the VASA Provider