Unable to login to DSM appliance version 2.2 UI as Active Directory user it fails with the error "Invalid Username/Password"
search cancel

Unable to login to DSM appliance version 2.2 UI as Active Directory user it fails with the error "Invalid Username/Password"

book

Article ID: 396010

calendar_today

Updated On:

Products

VMware Data Services Manager

Issue/Introduction

After deploying a DSM appliance version 2.2 the login as an Active Directory user to the DSM UI fails with the error "Invalid Username/Password".

The plugin appears to be working fine, communicating with the vCenter correctly and connected to Active Directory server. 


Symptoms:

Currently no message or alert will appear for this in the GUI.

In the log provider/provider.log you may see the following message:

Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used: 60000 ms.
        at java.naming/com.sun.jndi.ldap.LdapRequest.getReplyBer(Unknown Source)
        at java.naming/com.sun.jndi.ldap.Connection.readReply(Unknown Source)
        at java.naming/com.sun.jndi.ldap.LdapClient.getSearchReply(Unknown Source)
        at java.naming/com.sun.jndi.ldap.LdapClient.search(Unknown Source)
        at java.naming/com.sun.jndi.ldap.LdapCtx.doSearch(Unknown Source)
        at java.naming/com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
        at java.naming/com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
        at java.naming/com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
        at java.naming/com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
        at java.naming/javax.naming.directory.InitialDirContext.search(Unknown Source)

Environment

VMware Data Services Manager 2.2

Cause

The environment is configured with a single AD domain with a very large number of  groups in the AD and the recursive filter for nested group objects is  significantly impacting the query speed.

This is fixed in DSM appliance version 2.2.2.

Resolution

Update DSM appliance to version 2.2.2 to resolve the issue.