Logging in with a user@vSphere.local to the vSphere Web Client 5.5 fails with the error: Provided credentials are not valid
search cancel

Logging in with a [email protected] to the vSphere Web Client 5.5 fails with the error: Provided credentials are not valid

book

Article ID: 309576

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Logging in as a user into the vSphere.local domain for vCenter Single Sign-On fails.
  • Logging into the vSphere Web Client, you see the error:

    Provided credentials are not valid.

  • The vmware-sts-idmd.log file (located at: C:\ProgramData\VMware\CIS\logs\vmware-sso) contains entries similar to:
01:41:58,535 WARN [LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 49
01:41:58,535 ERROR [WinLdapClientLibrary] Failed ldap_bind_s().
com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid Credentials
LDAP error [code: 49]

at com.vmware.identity.interop.ldap.LdapErrorChecker$28.RaiseLdapError(LdapErrorChecker.java:404)
at com.vmware.identity.interop.ldap.LdapErrorChecker.CheckError(LdapErrorChecker.java:826)
at com.vmware.identity.interop.ldap.WinLdapClientLibrary.CheckError(WinLdapClientLibrary.java:728)
at com.vmware.identity.interop.ldap.WinLdapClientLibrary.ldap_bind_s(WinLdapClientLibrary.java:247)
at com.vmware.identity.interop.ldap.LdapConnection.bindConnection(LdapConnection.java:132)
at com.vmware.identity.idm.server.ServerUtils.getLdapConnection(ServerUtils.java:302)
at com.vmware.identity.idm.server.ServerUtils.getLdapConnectionByURIs(ServerUtils.java:213)
at com.vmware.identity.idm.server.provider.BaseLdapProvider.getConnection(BaseLdapProvider.java:230)
at com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider.authenticate(VMwareDirectoryProvider.java:322)
at com.vmware.identity.idm.server.IdentityManager.authenticate(IdentityManager.java:2266)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)


Environment

VMware vSphere Web Client 5.5.x
VMware vCenter Server 5.5.x

Cause

This issue occurs due to non-ASCII characters in the password for a user account located on the vSphere.local domain native to vCenter Single Sign-On. Also when using an account other than the [email protected]

Resolution

This is a known issue affecting the vSphere Web Client and vCenter Single Sign-On in Vmware Vcenter Server 5.5. Currently, there is no resolution.

To work around this issue, ensure the password for user@vsphere.local contains only ASCII characters.


Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
For more information if you are experiencing this issue with the [email protected] account for vSphere 5.5, see:
vSphere 5.5 Single Sign-On [email protected] password issues
Unable to log in to vCenter Server Appliance 5.5 if username or group name contains letters with accents