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

Importing a newly created STS cert chain fails with an error: A vCenter Single Sign-On error occurred (67362)

Last Updated: 2/18/2020Categories: TroubleshootingTotal Views: 8556Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After creating a new sts signing certificate chain as per Generate a New STS Signing Certificate on the Appliance, importing the certificate chain using the Web Client fails

You see the following error on the Web Client:   "A vCenter Single Sign-On error occurred"

The sts certificate is in the correct pk12 format

Cause

In an upgraded vCenter Server, the old sts cert is retained in the STS_INTERNAL_SSL_CERT store. The documentation Generate a New STS Signing Certificate on the Appliance expects that the MACHINE_SSL_CERT will be used when creating the sts cert but instead the creation process references the MACHINE_CERT in the STS_INTERNAL_SSL_CERT store.

Impact / Risks

Ensure you Snapshot the vCenter Server Appliance. If you have external replicating PSCs, shut them all down and snapshot all nodes including vCenter node.

Resolution

To solve the issue follow the steps given below:

Obtain the current rootCA cert:  /usr/lib/vmware-vmca/bin/certool --getrootca --cert=/tmp/cacert.crt

Save this as cacert.crt on the appliance at your desired location; /tmp/ is provided in the above command as an example.

Replace the sts_internal_ssl_cert with the machine cert from the MACHINE_SSL_CERT store. Implement the commands below as you see them one by one:

/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store MACHINE_SSL_CERT --alias __MACHINE_CERT > ~/machine.crt
/usr/lib/vmware-vmafd/bin/vecs-cli entry getkey --store MACHINE_SSL_CERT --alias __MACHINE_CERT > ~/machine.key
/usr/lib/vmware-vmafd/bin/vecs-cli entry getcert --store STS_INTERNAL_SSL_CERT --alias __MACHINE_CERT > ~/sts_internal_backup.crt
/usr/lib/vmware-vmafd/bin/vecs-cli entry getkey --store STS_INTERNAL_SSL_CERT --alias __MACHINE_CERT > ~/sts_internal_backup.key
/usr/lib/vmware-vmafd/bin/vecs-cli entry delete --store STS_INTERNAL_SSL_CERT --alias __MACHINE_CERT -y
/usr/lib/vmware-vmafd/bin/vecs-cli entry create --store STS_INTERNAL_SSL_CERT --alias __MACHINE_CERT --cert ~/machine.crt --key ~/machine.key

4. Create the new sts cert. The document Generate a New STS Signing Certificate on the Appliance assumes that the cert at  /etc/vmware-sso/keys/ssoserverRoot.crt is the same as the rootca. But  when you are on an upgraded as opposed to a newly deployed vCenter Server Appliance, they can be different. So, when going through Generate a New STS Signing Certificate on the Appliance  again to create the new sts cert, replace /etc/vmware-sso/keys/ssoserverRoot.crt with <path>/cacert.crt wherever you see it in the opnssl commands
5. Now when importing the  root-trust.jks as per Refresh the Security Token Service Certificate it should succeed.
6. Restart all vCenter and PSC services
7. Delete the old sts signing certs from the web client

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

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 vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant