Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Adding Custom Certificate on ESXi hosts through CLI (56441)

Last Updated: 4/11/2024Categories: How toTotal Views: 44698Language:
Chinese (Simplified)JapaneseEnglish

16 like this article

Subscribe to get an email
newsletter with new updates

16 people found this helpful Please provide article feedback:

Details

The KB outlines the steps to add custom certificate as the root CA to the ESXi trusted domain without bypassing the certificate based SSL authentication. The root CA can then be used to sign other intermediate CERTs and/or the host certificate file (i.e. private key – public key pair).Before making any changes you may like to validate with customer if they are using any third party trusted certificates.

Solution

Process to add Custom Certificate on ESXi hosts through CLI:

Set the vCenter Server to custom certificate mode by following the steps in the link outlined here .

Ensure the custom Root certificate is retrieved in advance before proceeding.

Place the ESXi host in maintenance mode (Evacuate all data to other hosts)

Disconnect the ESXi host from the cluster.

SSH into the ESXi host

Run this command to take a backup of the castore.pem file:

# cp /etc/vmware/ssl/castore.pem /etc/vmware/ssl/castore.pem.bak

Note: The system will be rebooted in the following steps. If user wants to access the castore.pem.bak in future probably, please copy (using scp) this file out from the ESXi host.

Copy the Root certificate to /etc/vmware/ssl/Root.cer

Note: If the user has one or more intermediate certificate authorities, the Root certificate must be a chain of all intermediate certificates and root certificate.

Append the Root certificate to castore.pem file by command:

# cat Root.cer >> castore.pem

Note: User can append multiple root certs however the ESXi host certificate file should be signed by one root certificate ( the pem file should contain, the machine ssl, the intermediate ssl, and the root cert)

Delete the Root certificate by command:

# rm Root.cer

Replace the default rui.crt and rui.key with trusted CA-signed certificate and key per Replace the default Certificate and Key from the ESXi Shell.

After applying the custom certificate in ESXi hosts, the user needs to persist those changes into the system disk by running /sbin/auto-backup.sh

Restart the ESXi host.

Reconnect the ESXi host back to the original cluster.

Exit maintenance mode.

NOTE: This process can be used on a vSAN cluster to authenticate hosts utilized in the vSAN cluster. As Chrome IE and Edge does not give option to download the PEM CERTS , the customer may use Mozilla Firefox for Windows.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESXi

Related Versions:

VMware vSphere ESXi 7.0.x

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant