Follow these steps to troubleshoot when you are unable to log in with a valid login ID that exists in the LDAP repository.
The following example of the virtual member manager trace shows the entity that causes login failure:
cn=wastest,ou=Users,o=www,ou=Users,o=www
However, the LDAP search result shows the actual entity that causes the failure:
cn=wastest,ou=Users,o=www
In this example, the problem is caused by incorrect searchBase configuration. The searchBase ou=Users,o=www is appended twice.
The incorrect searchBase configuration in the wimconfig.xml file for this example is shown here:
<config:baseEntries name="ou=Users,o=www" nameInRepository=""/>
Correct the searchBase configuration for the LDAP repository as shown here for the example described in the previous section:
<config:baseEntries name="ou=Users,o=www" nameInRepository="ou=Users,o=www"/>