Configuring CA signed certificates for ESXi 5.0 hosts
This article guides you through the configuration of Certificate Authority (CA) certificates for a ESXi 5 host. The instructions provided help you to:
eliminate common causes for problems during certificate implementation, including configuration steps and details.
avoid misconfiguration in implementation of custom certificates in your environment.
Note: This article is part of an overall resolution path. Before following the steps in this article, see Implementing CA signed SSL certificates with vSphere 5(2015383).
Creating CA assigned certificates for an ESXi 5.0.x host is a complex task. In many organizations it is required to maintain proper security for regulatory requirements. Each server must be unique to the component as it ties to the fully qualified domain name of the server. As such you cannot just take a single certificate and apply it to all hosts. Wildcard certificates are currently not supported, but even if they were, it is much more secure to have a proper certificate for each host. There are several different work flows required for a successful implementation:
Creating the certificate request
Getting the certificate
Installation and configuration of the certificate on the ESXi host
All must be followed to ensure successful implementation of a custom certificate for an ESXi 5 host. Before attempting these steps ensure that:
The environment is a vSphere 5.0
The steps in the configuring SSL article have been followed
You have an SSH client (such as Putty) installed
You have a SFTP/SCP client (such as WinSCP) installed
The ESXi 5.0 hosts are a part of a Cluster with VMware HA Enabled
To avoid a known issue with VMware HA, make sure you are running vCenter 5.0 U1 or later.
Generating a certificate request
To generate a certificate request for an ESXi 5 host follow these steps:
Launch a command prompt and navigate into the OpenSSL directory as previously configured in the Configuring OpenSSL article. By default this is C:\OpenSSL-Win32\bin.
Note: there will be no prompts because all information was provided in the openssl.cfg file as configured in the previous article.
This will create the certificate request rui.csr.
Once rui.csr is created continue on to the getting the certificate section of this document.
Getting the certificate
After the certificate request is created, the certificate must be given to the certificate authority for generation of the actual certificate. The authority will present a certificate back, as well as a copy of their root certificate, if necessary. For the certificate chain to be trusted, the root certificate must be installed on the server.
Follow the appropriate section below for the steps for the certificate authority in question.
For Commercial CAs, complete these steps:
Take the certificate request (rui.csr as generated above) and send it to the authority in question.
The authority will send back the generated certificate.
Install the root certificate onto the vCenter server before proceeding to the Installation of the certificate section of this document.
For Microsoft CAs complete these steps:
Login to the Microsoft CA certificate authority web interface. By default, it is http:///CertSrv/
Click Request a certificate.
Click advanced certificate request.
Click Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
Open the certificate request in a plain text editor.
Copy from -----BEGIN CERTIFICATE REQUEST----- to -----END CERTIFICATE REQUEST----- into the Saved Request box.
Click Web Server when selecting the Certificate Template.
Click Submit to submit the request.
Click Base 64 encoded on the Certificate issued screen.
Click Download Certificate.
Save the certificate on the desktop of the server as rui.crt. Once complete proceed to the installation of the certificate request section of this document to complete the configuration of the custom certificate.
For OpenSSL Self-Signed Certificates complete these steps:
Create the certificate by running the following command:
This command will output the certificate as needed to proceed to the installation and configuration section of this article.
Installation and configuration of the certificate on the ESXi Host
After the certificate is created, complete the installation and configuration of the certificate on the ESXi 5 host:
Login to vCenter
Put the host into Maintenance Mode.
Navigate to the console of the server to enable SSH on the ESXi 5 host.
Press F2 to log in to the Direct Console User Interface (DUCI).
Click Troubleshooting options > Enable SSH.
Login to the host and then navigate to /etc/vmware/ssl.
Copy the files to a backup location, such as a VMFS volume.
Login to the host with WinSCP and navigate to the /etc/vmware/ssl directory.
Delete the existing rui.crt and rui.key from the directory.
Copy the newly created rui.crt and rui.key to the directory using Text Mode or ASCII mode to avoid the issue of special characters ( ^M) appearing in the certificate file.
Type less rui.crt to validate that there are no extra characters.
Note: There should not be any erroneous ^M characters at the end of each line.
Switch back to the DCUI of the host and select Troubleshooting Options > Restart Management Agents.
When prompted press F11 to restart the agents. Wait until they are restarted.
Press ESC several times until you logout of the DCUI.
Exit the host from Maintenance Mode.
Once complete, the host is be made available and successfully rejoins the HA cluster.
If you are not running vCenter 5.0 U1 or later, the configuration of VMware HA will fail with an error. This is due to a known issue where the new SSL thumbprint is not updated in the vCenter database for VMware HA. For more information on this error, see After upgrading to vSphere5, you see the HA error: vSphere HA Cannot be configured on this host because its SSL thumbprint has not been verified (2006210). The easiest way to resolve this issue is to follow the Alternative Workaroundsection of the KB article, which uses HostReconnect.pl (attached to the article) to reconnect the servers to vCenter updating the expected SSL thumbprint in the vCenter database. Once complete run a reconfigure of vSphere HA for the configuration to proceed successfully.
The configuration of the custom certificate is now complete. Repeat these steps for each host which needs to have a custom certificate.