JDK 1.8 Update 141 and 144 fails to make an SSO connection to the vSphere Management and the vSphere Automation API
search cancel

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

book

Article ID: 339031

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

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 = ""
--> }


Environment

VMware vSphere Web Services SDK 4.1
VMware vSphere Guest SDK 4.0

Resolution

Currently, there is no resolution.


Workaround:
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 uses username/password authentication instead of SSO.

Note: The issue is fixed in the following versions of JDK:

8u192
8u191
8u181
8u172
8u171
8u162
8u152
emb-8u181
emb-8u171

For more information, see https://bugs.openjdk.java.net/browse/JDK-8186441.


Additional Information

For more information, see these 8u141 Update Release Notes.
 
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.