The first action is to discover the ldapAuthentication.rootContext value (in this example will be the base DN) for within the $OIAHOME/conf/jdbc.properties file. To achieve this, you can use the dsquery function that comes OOTB with Windows Server 2003. To use this, simply type:

dsquery user

You may gets a response like this:

"CN=Administrator,CN=Users,DC=SenaSystems,DC=local"
"CN=Guest,CN=Users,DC=SenaSystems,DC=local"
"CN=SUPPORT_388945a0,CN=Users,DC=SenaSystems,DC=local"
"CN=OIMUser,CN=Users,DC=SenaSystems,DC=local"
"CN=David Davids,OU=anotherOU,OU=testingOU,DC=SenaSystems,DC=local"
"CN=rbacxadmin,CN=Users,DC=SenaSystems,DC=local"
"CN=auditor,CN=Users,DC=SenaSystems,DC=local"
"CN=ab14156,CN=Users,DC=SenaSystems,DC=local"

In this example, I wish to leverage off the rbacxadmin account, which will be my admin account. If this is the case, my ldapAuthentication.rootContextwill beCN=Users,DC=SenaSystems,DC=local. We can then use this information within the ldap.properties file proceeding with the following changes.

This is the original segment from within the file:

# Properties file with ldap authenticaton related settings
ldapAuthentication.defaultRole=ROLE_AUTHENTICATED_PRINCIPAL

ldapAuthentication.enabled=false
ldapAuthentication.tryNextProviderIfNoAuthenticated=false
ldapAuthentication.stopIfCommunicationError=true

#Multiple urls can be specified using ; as delimeter
#ldapAuthentication.url=ldap\://localhost:389/DC=vaau,DC=corp,DC=net

ldapAuthentication.url=ldap\://localhost:389/
ldapAuthentication.rootContext=DC=vaau,DC=corp,DC=net

Now change this to:

# Properties file with ldap authentication related settings
ldapAuthentication.defaultRole=ROLE_AUTHENTICATED_PRINCIPAL

ldapAuthentication.enabled=true
ldapAuthentication.tryNextProviderIfNoAuthenticated=false
ldapAuthentication.stopIfCommunicationError=true

#Multiple urls can be specified using ; as delimeter
#ldapAuthentication.url=ldap\://localhost:389/DC=vaau,DC=corp,DC=net

ldapAuthentication.url=ldap\://172.16.128.129:389/
ldapAuthentication.rootContext=CN=Users,DC=SenaSystems,DC=local

Restart the web server and test if you can connect

About the author