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 database repository login ID
Follow these steps to troubleshoot when you are unable to log in with a valid login ID that exists in the database repository.
Problem
The trace shows the cause of the login failure:
com.ibm.websphere.wim.exception.EntityNotFoundException: CWWIM4001E The 'o=default organization/null' entity was not found.Two possible reasons for the login failure are listed next.
- The base entry specified when adding database repository to virtual member manager is different from the one specified when setting up the database.
The following example shows that the dn value o=database.org is specified during database repository setup. This example is broken into multiple lines for illustration purposes only.
wsadmin>$AdminTask setupIdMgrDBTables {-schemaLocation "WAS_HOME\etc\wim\setup" -dbPropXML "WAS_HOME\etc\wim\setup\wimdbproperties.xml" -databaseType db2 -dbURL jdbc:db2:wimDB -dbDriver com.ibm.db2.jcc.DB2Driver -dbAdminId <db2User> -dbAdminPassword <db2UserPwd> -dn o=database.org -reportSqlError true}However, a different base entry is specified when adding the database repository to virtual member manager, which is wrong:
wsadmin>$AdminTask addIdMgrRepositoryBaseEntry {-id DB2Repos -name "o=default organization"}- The following command might have been used to add the database repository base entry:
wsadmin>$AdminTask addIdMgrRepositoryBaseEntry {-id DB2Repos -name "o=default organization" -nameInRepository="o=database.org" }In this example, the values of both –name and nameInRepository must be the same for a database repository.
Solution
Correct the invalid configuration in the wimconfig.xml file, so that the values of both -name and -nameInRepository are the same for the database repository.
For example, to correct the invalid configuration shown in the examples in the previous section, make the following change:
<config:baseEntries name="o=database.org"/>
Related topics
Unable to log in with a valid LDAP repository login ID
Parent topic: Authentication issues and limitations