Search the VMware Knowledge Base (KB)
View by Article ID

JDK 1.8 Update 141 and 144 fails to make an SSO connection to the vSphere Management and the vSphere Automation API (2151706)

  • 1 Ratings


After the SSO connection fails, you can see this errors in the VPXD log:

ERROR task-internal... vim.SessionManager.loginByToken: vim.fault.InvalidLogin:
--> Result:
--> (vim.fault.InvalidLogin) {
--> faultCause = (vmodl.MethodFault) null,
--> msg = ""
--> }


To work around this issue, downgrade the JDK. However, most customers consider that not only an inconvenience but also a security issue.

To work around this issue for vSphere Management API (not vSphere Automation), use of the --basic-connection option to disable SSO.
For example: run.bat com.vmware.general.SimpleClient --url https://vCenterIP/sdk --username user --password pass --ignorecert --basic-connection
This workaround actually uses username/password authentication instead of SSO.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 1 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 1 Ratings