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

NSX cannot connect to SSO in an environment with multiple PSCs or STS certificates after installing or upgrading to NSX-V 6.4.2 (57770)

Last Updated: 9/11/2018Categories: TroubleshootingTotal Views: 8272Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX is not able to connect to the vCenter SSO server after deployment of NSX 6.4.2 when:

Multiple PSCs are involved OR

An embedded PSC with multiple certificate chains are involved

Configuring the SSO Lookup Service fails with the following error in vsm.log:

2018-08-28 17:28:53.178 CEST INFO TaskFrameworkExecutor-2 X509TrustChainKeySelector:190 - Failed to find trusted path to signing certificate <CN=[SSO hostname]>
java.security.cert.CertPathBuilderException: Unable to find certificate chain.

At the NSX Manager Virtual Appliance Management Webpage, you will observe the following error under “Manage vCenter registration option:

NSX Management Service operation failed. ( Initialization of Admin Registration Service Provider failed. Root Cause: Signature validation failed )
Lookup Service https://sc2-test-psc01.eng.xyz.com:443/lookupservice/sdk presented an SSL certificate with the following thumbprint:
9B:48:5B:BC:60:01:13:4C:DE:AD:BE:AF:54:56:5B:CE:61:A8:FE:52
Proceed with this certificate?

Cause

This occurs when you have multiple trusted chain certificates, because the upgraded NSX client code uses only the first chain to configure the trust store.

Note -  that multiple chains can come in play when there are multiple PSC nodes with different Tenant Credentials. This can be hit when vCenter has been upgraded from a previous version where different PSCs had different signing credentials. To support that scenario, we need to include chains from both issuers, to allow the token to be validated against PSC nodes with different signing credentials.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.3, available at VMware Downloads.

Workaround

To work around this issue if you are not able to upgrade:

A script has been developed by VMware that replaces the JAR file in the NSX manager. The workaround requires a signed script to be executed using REST API call to NSX Manager.

Download the attached PscAndNetXFix.encoded file.

Run the following POST call on NSX Manager via one of the two options below.

Option 1: Postman
Method: POST
URL: https://nsxmgr_ip/api/1.0/services/debug/script
Authentication: Basic authentication (Username: admin)Expected Response: 200
Headers: content-type - application/xml
Body: copy contents of the attached file PscAndNetXFix.encoded

Note: During copy/paste of the contents into the body, make sure no extra line/characters get added at the end in order to have the API run successfully. The content of the PscAndNetXFix is roughly 11 MB, opening the file, copying the content and running the API call all take time to process. Do not interrupt the API call. Proceed to Step #3 only if the response is 200.

Option 2: CURL (Run from your local machine or the node that contains the PscAndNetXFix.encoded file)

curl -k -X POST -H "Content-Type: application/xml" -d "@PscAndNetXFix.encoded" -u user:password https://nsxmgr_ip/api/1.0/services/debug/script

3. After the running the API, restart the NSX management service in the NSX UI.
4. Once NSX management service has started, re-register the lookup service in NSX UI.

Note: If the above workaround fails, please file a support request with VMware support.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

PscAndNetXFix

vsphere-1.0

vsphere-1.0.jar

PscAndNetXFix.encoded script

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

Take Our Survey

Support Assistant