4.6

Table Of Contents
Configuring Certificate Authentication 7
You can configure certificate authentication for View Connection Server instances, security servers, and View
Transfer Server instances.
This chapter includes the following topics:
n
“Replacing the Default Certificate,” on page 79
n
“Add keytool and openssl to the System Path,” on page 80
n
“Use an Existing PKCS#12 Certificate and Private Key,” on page 80
n
“Convert a PKCS#12 Keystore to JKS Format,” on page 82
n
“Creating a New SSL Certificate,” on page 82
n
“Configure a View Connection Server Instance or Security Server to Use a New Certificate,” on
page 85
n
“Configure a View Transfer Server Instance to Use a New Certificate,” on page 86
n
“Configure SSL for Client Connections,” on page 87
n
“Configure SSL for View Transfer Server Communications,” on page 88
n
“Using Group Policy to Configure Certificate Checking in View Client,” on page 88
Replacing the Default Certificate
A default server SSL certificate is generated when you install View Connection Server. You can use the default
certificate for testing purposes.
IMPORTANT Replace the default certificate as soon as possible. The default certificate is not signed by a
commercial Certificate Authority (CA). Use of certificates that are not signed by a CA can allow untrusted
parties to intercept traffic by masquerading as your server.
View Connection Server instances, security servers, and View Transfer Server instances require a server SSL
certificate if they receive SSL connections.
n
If you enable SSL for client connections, client-facing View Connection Server instances and security
servers require a server SSL certificate.
n
If you enable SSL for local mode operations and desktop provisioning, View Transfer Server instances
require a server SSL certificate.
n
If you configure smart card authentication in VMware View, client-facing View Connection Server
instances and security servers require a root CA certificate in addition to a server SSL certificate.
VMware, Inc.
79