5.2

Table Of Contents
4 Modify the SSLCertWinCertFriendlyName value and type the certificate Friendly name to be used by the
PSG.
For example: pcoip
If you use the same certificate as the View server, the value must be vdm.
5 Restart the VMware View PCoIP Secure Gateway service to make your changes take effect.
What to do next
Verify that View Client devices continue to connect to the PSG.
If you are using a security scanner for compliance testing, scan the PSG port.
(Optional) Force a CA-Signed Certificate to Be Used for Connections to the PSG
You can ensure that all View Client connections to the PSG use the CA-signed certificate for the PSG instead
of the default legacy certificate. This procedure is not required to configure a CA-signed certificate for the
PSG. Take these steps only if it makes sense to force the use of a CA-signed certificate in your View
deployment.
In some cases, the PSG might present the default legacy certificate instead of the CA-signed certificate to a
security scanner, invalidating the compliance test on the PSG port. To resolve this issue, you can configure
the PSG not to present the default legacy certificate to any device that attempts to connect.
IMPORTANT Performing this procedure prevents all legacy clients from connecting to this View server over
PCoIP.
Prerequisites
Verify that all client devices that connect to this View server, including thin clients, run View Client 5.2 for
Windows or View 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 View PCoIP Secure Gateway service to make your changes take effect.
View Transfer Server and SSL Certificates
You do not have to configure SSL certificates for View Transfer Server if you are installing View 5.1 or later.
A default, self-signed certificate is installed with View Transfer Server that View Connection Server uses to
handle secondary connections to View clients.
When you add View Transfer Server to View, View Connection Server establishes a trust relationship with
View Transfer Server. Communications between View Connection Server and View Transfer Server use Java
Message Service (JMS). Messages containing sensitive data are encrypted.
When a View client requests a data transfer operation, which requires connecting to View Transfer Server,
View Connection Server sends the thumbprint of the View Transfer Server certificate to the client. When the
client connects to the Apache server that is associated with View Transfer Server, View Client verifies that
the thumbprint passed from View Connection Server matches the certificate thumbprint on the Apache
server.
Chapter 7 Configuring SSL Certificates for View Servers
VMware, Inc. 87