Architecting a vCloud Availability for vCloud Director Solution : vCloud Availability Management Components : 4.3 Cloud Proxy : 4.3.3 Cloud Proxy Certificates
   
4.3.3 Cloud Proxy Certificates
A publicly trusted certificate for the fully qualified domain name of cloud proxy VIP must be imported to the cloud proxy cell with the http alias. Another certificate must be present with the alias consoleproxy even though it will be unused. This is because the cloud proxies should not be used for VM console proxy sessions. Both certificates are imported with the same process as vCloud Director cell certificates.
Because each cloud proxy is accessed from the internet under two different FQDNs (cloud proxy VIP in Table 4 and specific cloud proxy FQDN in Table 5), the http certificate must match both FQDNs. The easiest approach is to use a wild card certificate. If that is not possible, certificates with Subject Alternate Name (listing both FQDNs) can be used instead.
Table 6. FQDN Example
Attribute
Specification
vCloud Director UI/API
vcloud.example.com
vCloud Remote Console Proxy
console.example.com
vCloud Availability Portal
availability.example.com
Cloud Proxy VIP
vip.proxy.example.com
Cloud Proxy 1
cp1.proxy.example.com
Cloud Proxy 2
cp2.proxy.example.com
Certificate CN on Cloud Proxy Nodes
*.proxy.example.com