Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Troubleshoot and Support > Support issues and limitations > Authentication issues and limitations
Unable to log in with a valid LDAP repository login ID
Follow these steps to troubleshoot when you are unable to log in with a valid login ID that exists in the LDAP repository.
Problem
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=wwwHowever, the LDAP search result shows the actual entity that causes the failure:
cn=wastest,ou=Users,o=wwwIn this example, the problem is caused by incorrect base entry configuration. The base entry ou=Users,o=www is appended twice.
The incorrect base entry configuration in the wimconfig.xml file for this example is shown here:
<config:baseEntries name="ou=Users,o=www" nameInRepository=""/>
Solution
Correct the base entry 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"/>Important: Do not specify an empty string ("") as value for the nameInRepository attribute of base entry, because most LDAP repositories (except Domino) do not support root mode.
Related topics
Unable to log in with a valid database repository login ID
Parent topic: Authentication issues and limitations