Search the VMware Knowledge Base (KB)
View by Article ID

Implementing CA signed SSL certificates with vSphere 5.x (2034833)

  • 65 Ratings


This article provides information on manually configuring Certificate Authority (CA) signed SSL certificates in a vSphere 5.1 or vSphere 5.5 environment. VMware has released a tool to automate much of the described process below. Please see Deploying and using the SSL Certificate Automation Tool 1.0.x (2041600) before following the steps in the article.

In the case that you are unable to use the tool this article helps you eliminate common causes for problems during certificate implementation, including configuration steps and details, and helps avoid common misconfigurations in the implementation of custom certificates in your environment.

Note: This article is specifically for vSphere 5.1 and vSphere 5.5. If you are using vSphere 5.0, see Implementing CA signed SSL certificates with vSphere 5.0 (2015383).


Important: Ensure that you are using OpenSSL Version 0.9.8. If you are using a different version, the SSL implementation would fail.

Configuring CA signed certificates is a challenge with vSphere as with any complex enterprise environment. Securing an environment is a requirement in many large organizations. You need either public certificates (such as Verisign or Globaltrust), Microsoft CA certificates, or OpenSSL CA certificates to ensure secure communication.

This article provides steps to allow configuration of these certificates on vSphere components in an environment. This article also assumes that all components are installed and running already with self-signed certificates.

Ensure that you validate each step below. Each step provides instructions or a link to a document that provides information on configuring the certificates in your environment.

Core vSphere components

  1. Create a new Certificate Authority template for certificate generation. For more information, see Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 5.x (2062108).

  2. Generate certificate requests and certificates for each of the vCenter Server components. For more information, see:

  3. Replace the vCenter Single Sign-On certificates. For more information, see:

  4. Replace the Inventory Service certificates. For more information, see:

  5. Replace the vCenter Server 5.x certificates. For more information, see:

  6. Replace the vSphere Web Client certificates. For more information, see:
  7. Replace ESXi 5.x host certificates. For more information, see Configuring CA signed SSL certificates with ESXi 5.x hosts (2015499).

Peripheral vSphere components

  1. Replace the vSphere Update Manager Certificates. For more information, see Configuring CA signed SSL certificates for VMware Update Manager in vSphere 5.1 and 5.5 (2037581).

  2. Replace the vSphere Auto Deploy Certificates. For more information, see Configuring CA signed SSL certificates for vSphere Auto Deploy in vSphere 5.x (2073588).

Additional Information

If your issue persists even after trying these steps:

See Also

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.


  • 65 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 65 Ratings