Loading...
Loading...
This article guides you through the configuration of Certificate Authority (CA) certificates for a ESXi 6.x/7.0 host. The instructions provided helps you eliminate errors or common causes for problems during certificate implementation, including configuration steps and details, and avoid misconfiguration in implementation of custom certificates in your environment. ESXi hosts that are upgraded from vSphere 5.x to vSphere 6.x continue to use their CA signed certificates if they were replaced in the previous versions. However, ESXi 5.x hosts that were running self-signed certificates and then upgraded to vSphere 6.x will have their certificates regenerated using VMware-signed. For more information, see Host Upgrades and Certificates in the vSphere Security guide. This article helps you to replace ESXi certificate. This article will help you to replace ESXi SSL custom certificateThis article help you yo add/install/change and generate ESXi host certificate This article help you to import and replace certificate for ESXi custom certificate
Note: This article is part of several resolution paths. Before performing the steps in this article, see Implementing CA signed SSL certificates in vSphere 6.0 (2111219) Creating CA assigned certificates for an ESXi 6.x/7.0 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. ESXI 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: Generating the certificate requestGetting the certificateInstallation and configuration of the certificate on the ESXi host These steps must be followed to ensure successful implementation of a custom certificate for an ESXi 6.x/7.0 host. Before attempting these steps ensure that: You have a vSphere 6.x/7.0 environment.You have followed the steps in Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0 (2112009).You have an SSH client (such as Putty) installedYou have a SFTP/SCP client (such as WinSCP) installed Generating a Certificate Request To generate a certificate request for an ESXi 6.x/7.0 host: Open a command prompt and navigate to the OpenSSL directory as previously configured using the Configuring OpenSSL for installation and configuration of CA signed certificates in the vSphere environment article. By default this is C:\OpenSSL-Win32\bin.Run the command: openssl req -new -nodes -out rui.csr -keyout rui-orig.key -config openssl.cfg Note: There are no prompts because all information was provided in the openssl.cfg file as configured in the previous article. This creates the certificate request rui.csr. Convert the Key to be in RSA format by running these command: openssl rsa -in rui-orig.key -out rui.key After rui.csr is created, proceed to Getting the certificate. Getting the Certificates After the certificate request is created, the certificate must be given to the certificate authority for generation of the actual certificate. The authority presents 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 for the steps for the certificate authority in question. For Commercial CAs: 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 in vCenter Server before proceeding to the Installation of the certificate section of this document. For Microsoft CAs: Note: For Windows Server 2003 CA's, Enterprise edition is required. Other Windows Server 2003 editions do not have the correct templates for exporting a valid SSL certificate. Create a custom template for certificate creation. For more information, see Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.x.Log in to the Microsoft CA certificate authority web interface. By default, it is http://servername/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 using a text editor.Copy the content from -----BEGIN CERTIFICATE REQUEST----- to -----END CERTIFICATE REQUEST----- into the Saved Request box.Select the custom template created in step 1.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. When complete, proceed to Installing and configuring the certificate on the ESXi host to complete the configuration of the custom certificate. Installing and configuring the certificate on the ESXi host After the certificate is created, complete the installation and configuration of the certificate on the ESXi 6.x/7.0 host: Note: Skip the first two steps if the ESXi is not part of vCenter Server (standalone host). Also, steps mentioned in "Process to update the vCenter Server database with the new certificate thumbprint" is not applicable for Standalone ESXi hosts. Log in to vCenter Server.Put the host into Maintenance Mode. Note: If the ESXi 6.x/7.0 connects to VC 6.x/7.0 after replacing its cert with this KB, the host certs will be replaced by VMCA signed certs. VC 6.x/7.0 needs to switch to custom certificate mode first. For more information, see Understanding Certificate Mode Switches.Navigate to the console of the server to enable SSH on the ESXi hostPress F2 to log in to the Direct Console User Interface (DCUI)Click Troubleshooting options > Enable SSHLog in to the host and then navigate to /etc/vmware/sslCopy the files to a backup location, such as a VMFS volumeLog in to the host with WinSCP and navigate to the /etc/vmware/ssl directoryDelete the existing rui.crt and rui.key from the directoryCopy 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 fileType vi 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 AgentsWhen prompted press F11 to restart the agents. Wait until they are restartedPress ESC several times until you logout of the DCUIExit the host from Maintenance Mode When complete, the host is made available and successfully rejoins the cluster.Note: If the host is a part of a View cluster, you may need to perform these steps after updating the certificates to update the vCenter Server database with the new certificate thumbprint: Process to update the vCenter Server database with the new certificate thumbprint: Log in to vCenter ServerPlace the host into the Maintenance ModeRight-click the host and click DisconnectRemove the disconnected host from the View clusterRecompose the View desktop(s) again on the existing hosts in the cluster and ensure that they recompose successfullyRight-click on the disconnected host and select ConnectAdd the host back to the clusterSet DRS to Manual (optional)Recompose the desktop on the host that was recently added back into the clusterIf step 9 is successful, set DRS back to Automatic, if required The configuration of the custom certificate is now complete. Repeat these steps for each host which needs to have a custom certificate.
VMware Skyline Health Diagnostics for vSphere - FAQIf you are receiving error "Failed to import new SSl certificate", please verify the MD5 check against the Private Key and the Certificate files, both should match if the Private Key belongs to the same certificate. Login to ESXi host using SSHUse below commands to run MD5 check openssl x509 -in <path to the Certificate file> -noout -modulus | openssl md5 openssl rsa -in <path to the Private Key file> -noout -modulus | openssl md5 Example (where certificate not matching with private key): # openssl x509 -in rui.crt -noout -modulus | openssl md5(stdin)= 55d84795791549fe72fc498c69f0dd2d# openssl rsa -in rui.key -noout -modulus | openssl md5(stdin)= 6b84b1c62e91dbfc6b9f9efa5d34fb86 Reviewing hostd log (/var/run/log/hostd.log) will help to identify the cause if the MD5 values are matching and still getting the same error during Import operation. Configuring CA signed certificates for ESXi 5.x hostsReplacing default certificates with CA signed SSL certificates in vSphere 6.xCreating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.0Read this article in different language here:ESXi 6.0 ホスト用の CA 署名証明書の構成为 ESXi 6.0 主机配置 CA 签名证书
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.