Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Guidelines for generating and importing an SSL certificate for the View Connection Server for View 5.0.1 and earlier (1008705)
Details
When installing a new SSL certificate on the View Connection Server, you experience these symptoms:
- You are unable to import an SSL certificate for the View Connection Server
- Importing an SSL certificate for the View Connection Server fails
- You see this error:
keytool error: java.security.KeyStoreException: TrustedCertEntry not supported
Solution
Note: This process only applies to VMware View versions 5.0 and earlier. For information on Configuring SSL Certificates in View 5.1, see the View Installation Guide and Using Microsoft Certreq to generate and import a signed certificate into View 5.1 (2032400).
To generate and import an SSL certificate on the View Connection Server:
Notes:
- Certificates are required only for client-facing systems, such as Standard, Replica, or Security servers.
- Information appearing within <brackets> represents variable information. Do not include the brackets when typing commands.
- View Manager 5.x supports pkcs and jks store types. Ensure to use the appropriate command based on the keystore type.
- Add keytool to the system path:
- In your View Connection Server or Security Server host, right-click My Computer and click Properties.
- Click the Advanced tab.
- Click Environment Variables.
- In the System variables group, select Path and click Edit.
- Type the path to the JRE directory in the Variable Value text box. For example, <install_directory>\VMware\VMware View\Server\jre\bin.
Note: Use a semicolon (;) to separate each entry from the other entries in the text box.
- Generate a Keystore and Certificate:
- Open a command prompt and run this command using keytool to generate a Keystore file using one of the following:
- pkcs key:
keytool -genkey -keyalg "RSA" -keystore <keys.p12> -storetype pkcs12 -validity 360 - 2048-bit pkcs key:
keytool -genkey -keyalg "RSA" -keystore <keys.p12> -storetype pkcs12 -validity 360 -keysize 2048 - jks key:
keytool -genkeypair -keyalg "RSA" -keysize 2048 -keystore <keys.jks> -storepass <secret>
- pkcs key:
- When keytool prompts you for the first and last name, type the fully qualified domain name (FQDN) that the client computers use to connect to the host.
- For JKS keystores, you will be prompted for a password. Use the same password used in the keytool command.
- Enter all other information to complete the keystore file. After keytool creates the Keystore file in the current directory, create a backup of the file.
- Open a command prompt and run this command using keytool to generate a Keystore file using one of the following:
- Obtain a Signed Certificate from a CA:
- Open a command prompt and run this command using keytool to create a CSR:
- pkcs key:
keytool -certreq -keyalg "RSA" -file <certificate.csr> -keystore <keys.p12> -storetype pkcs12 -storepass <secret> - jks key:
keytool -certreq -file <certificate.csr> -keystore <keys.jks> -storepass <secret>
Notes:- keytool creates the CSR file in the current directory.
- The keystore password must be at least 6 characters and cannot be left blank.
- pkcs key:
- Send the CSR to the CA according to the CA's enrollment process and request a certificate in PKCS# format.
Some CAs provide certificates only in PKCS#12 format. If you download a certificate in the PKCS#12 format, you must convert it to PKCS#7 format. Some vendors may use type rather than file type. In this case request a Tomcat certificate.
To convert a PKCS#12 certificate to PKCS#7 format:- Open the certificate file in Internet Explorer.
Note: Verify that the certificate chain is complete, including root and intermediate certificates.
- In the Details tab, click Copy to File. The Certificate Export wizard appears.
- Specify PKCS#7 format, include all certificates in the certification path, and then click Next.
- Specify a filename and click Next.
- Click Finish to export the file in PKCS#7 format.The file is saved with a .P7B extension.
If you completed this conversion use <certificate.p7b> instead of <certificate.p7> in the following steps with the keytool commands.
- Open the certificate file in Internet Explorer.
- Open a command prompt and run this command using keytool to create a CSR:
- Import the Signed Certificate into a Keystore file.
To import the Signed Certificate into a keystore file, open a command prompt and run this command using keytool:- pkcs key:
keytool -import -keystore <keys.p12> -storetype pkcs12 -storepass <secret> -keyalg "RSA" -trustcacerts -file <certificate.p7> - jks key:
keytool -importcert -keystore <keys.jks> -storepass <secret> -keyalg "RSA" -trustcacerts –file <certificate.p7>
Note: The storepass must be the same password that was used to generate the CSR in step 3.
- pkcs key:
- Configure the View Connection Server or Security Server to use the new certificate:
- Copy the Keystore file that contains your certificate to the SSL gateway configuration directory on the View Connection Server or Security Server host. For example, install_directory\VMware\VMware View\Server\sslgateway\conf\keys.p12.
- Add the keyfile and keypass properties to the locked.properties file in the SSL gateway configuration directory on the View Connection Server or Security Server host.
Note: If the locked.properties file does not exist, you must create it. - Set the keyfile property to the name of your Keystore file, using the appropriate file type.
- Set the keypass property to the password for your Keystore file. For example:
- pkcs key: keyfile=keys.p12
keypass=secret - jks key: storetype=jks
keyfile=keys.jks
keypass=secret
- pkcs key: keyfile=keys.p12
- Restart the View Connection Server or Security Server for the changes take effect.
- Ensure that the certificate is being used by checking the debug log on the server.
For log files locations, see Location of VMware View log files (1027744). You see lines similar to:
03:30:17,069 INFO <Thread-1> [q] The Secure Gateway Server is using SSL certificate store keys.p12 with password of 9 characters
03:30:17,819 INFO <Thread-1> [q] The Secure Gateway Server is listening on https://*:443
To configure another Security Server:
Note: These instructions only apply to the file types in the example. For more information, see the Configuring SSL certificates for View Servers.
- Copy the Keyfile and certificate.p7 files to the root of C: on the additional server.
- Set the environmental path for the keytool to C:\Program Files\VMware\VMware View\Server\jre\bin.
- Import the certificate with:
- pkcs key:
keytool -import -keystore <keys.p12> -storetype pkcs12 -storepass <secret> -keyalg "RSA" -trustcacerts -file <certificate.p7> - jks key:
keytool -import -keystore <keys.jks> -storepass <secret> -keyalg "RSA" -trustcacerts -file <certificate.p7>
- pkcs key:
- Copy the keyfile file to C:\Program Files\VMware\VMware View\Server\sslgateway\conf.
- Modify the locked.properties file and add these lines:
- pkcs key: keyfile=keys.p12
keypass=secret - jks key: storetype=jks
keyfile=keys.jks
keypass=secret
Note: storetype is required if using a type other than pkcs.
- pkcs key: keyfile=keys.p12
- Restart the View Security Service.
- To convert a Godaddy.com certificate, see Importing external Godaddy.com certificates (1004836).
- For information on Entrust SSL certificates, see Unable to import an Entrust SSL certificate in View 3.0.1 (1011237).
- For information on converting Comodo SSL certificates from a PFX (.p12 file) to a JKS (Java KeyStore), see Comodo article1283.
- For a third-party online certificate converter, seehttps://www.sslshopper.com/ssl-converter.html.
Tags
This Article Replaces
Update History
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

