6.0

Prerequisites
Verify that all client devices that connect to this server, including thin clients, run Horizon Client 5.2 for
Windows or Horizon Client 2.0 or later releases. You must upgrade the legacy clients.
Procedure
1 Start the Windows Registry Editor on the View Connection Server or security server computer where
the PCoIP Secure Gateway is running.
2 Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Teradici\SecurityGateway registry key.
3 Add a new String (REG_SZ) value, SSLCertPresentLegacyCertificate, to this registry key.
4 Set the SSLCertPresentLegacyCertificate value to 0.
5 Restart the VMware Horizon View PCoIP Secure Gateway service to make your changes take effect.
Setting View Administrator to Trust a vCenter Server or View
Composer Certificate
In the View Administrator dashboard, you can configure View to trust a vCenter Server or View Composer
certificate that is untrusted.
VMware strongly recommends that you configure vCenter Server and View Composer to use SSL
certificates that are signed by a CA. Alternatively, you can accept the thumbprint of the default certificate
for vCenter Server or View Composer.
Similarly, VMware recommends that you configure SAML 2.0 authenticators to use SSL certificates that are
signed by a CA. Alternatively, in the View Administrator dashboard you can configure View to trust an
untrusted SAML 2.0 server certificate by accepting the thumbprint of the default certificate.
Benefits of Using SSL Certificates Signed by a CA
A CA is a trusted entity that guarantees the identity of the certificate and its creator. When a certificate is
signed by a trusted CA, users no longer receive messages asking them to verify the certificate, and thin
client devices can connect without requiring additional configuration.
You can request an SSL server certificate that is specific to a Web domain such as www.mycorp.com, or you
can request a wildcard SSL server certificate that can be used throughout a domain such as *.mycorp.com. To
simplify administration, you might choose to request a wildcard certificate if you need to install the
certificate on multiple servers or in different subdomains.
Typically, domain-specific certificates are used in secure installations, and CAs usually guarantee more
protection against losses for domain-specific certificates than for wildcard certificates. If you use a wildcard
certificate that is shared with other services, the security of the VMware Horizon product also depends on
the security of those other services. If you use a wildcard certificate, you must ensure that the private key is
transferrable between servers.
When you replace the default certificate with your own certificate, clients use your certificate to authenticate
the server. If your certificate is signed by a CA, the certificate for the CA itself is typically embedded in the
browser or is located in a trusted database that the client can access. After a client accepts the certificate, it
responds by sending a secret key, which is encrypted with the public key contained in the certificate. The
secret key is used to encrypt traffic between the client and the server.
Chapter 6 Configuring SSL Certificates for View Servers
VMware, Inc. 79