Follow these steps to troubleshoot when you are unable to log in with a valid login ID that exists in the database repository.
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 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"}
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.
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.
<config:baseEntries name="o=database.org"/>