To set up SSL server certificates for View servers, you must perform several high-level tasks.

In a pod of replicated View Connection Server instances, you must perform these tasks on all instances in the pod.

The procedures for carrying out these tasks are described in the topics that follow this overview.

1

Determine if you need to obtain a new signed SSL certificate from a CA.

If your organization already has a valid SSL server certificate, you can use that certificate to replace the default SSL server certificate provided with View Connection Server, security server, or View Composer. To use an existing certificate, you also need the accompanying private key.

Starting Place

Action

Your organization provided you with a valid SSL server certificate.

Go directly to step 2.

You do not have an SSL server certificate.

Obtain a signed SSL server certificate from a CA.

2

Import the SSL certificate into the Windows local computer certificate store on the View server host.

3

For View Connection Server instances and security servers, modify the certificate Friendly name to vdm.

Assign the Friendly name vdm to only one certificate on each View server host.

4

On View Connection Server computers, if the root certificate is not trusted by the Windows Server host, import the root certificate into the Windows local computer certificate store.

In addition, if the View Connection Server instances do not trust the root certificates of the SSL server certificates configured for security server, View Composer, and vCenter Server hosts, you also must import those root certificates. Take these steps for View Connection Server instances only. You do not have to import the root certificate to View Composer, vCenter Server, or security server hosts.

5

If your server certificate was signed by an intermediate CA, import the intermediate certificates into the Windows local computer certificate store.

To simplify client configuration, import the entire certificate chain into the Windows local computer certificate store. If intermediate certificates are missing from the View server, they must be configured for clients and computers that launch View Administrator.

6

For View Composer instances, take one of these steps:

If you import the certificate into the Windows local computer certificate store before you install View Composer, you can select your certificate during the View Composer installation.

If you intend to replace an existing certificate or the default, self-signed certificate with a new certificate after you install View Composer, run the SviConfig ReplaceCertificate utility to bind the new certificate to the port used by View Composer.

7

If your CA is not well known, configure clients to trust the root and intermediate certificates.

Also ensure that the computers on which you launch View Administrator trust the root and intermediate certificates.

8

Determine whether to reconfigure certificate revocation checking.

View Connection Server performs certificate revocation checking on View servers, View Composer, and vCenter Server. Most certificates signed by a CA include certificate revocation information. If your CA does not include this information, you can configure the server not to check certificates for revocation.

If a SAML authenticator is configured for use with a View Connection Server instance, View Connection Server also performs certificate revocation checking on the SAML server certificate.