VERIFIED SOLUTION i

Resolve 'Unable to search the ldap with search base null' encountered while validating security bundle EngageOne Server 4.X

Issue

While validating EngageOne Server 4.XSecurity bundle, error 'Unable to search the ldap with search base null' is observed.

eos-security-validate.log - 

[WARN ] Following LDAP attributes could not be found: [mail]
[ERROR] Unable to search the ldap://152.144.227.88:389 with search base null and filter cn=users
java.lang.NullPointerException: null
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source) ~[na:1.8.0_25]
    at javax.naming.directory.InitialDirContext.getURLOrDefaultInitDirCtx(Unknown Source) ~[na:1.8.0_25]
    at javax.naming.directory.InitialDirContext.search(Unknown Source) ~[na:1.8.0_25]
    at javax.naming.directory.DirContext$search$0.call(Unknown Source) ~[na:na]
............
............
............
............
............
............
at org.codehaus.groovy.tools.GroovyStarter.main(GroovyStarter.java:131) [groovy-2.4.4.jar:2.4.4]
[ERROR] One or more properties are invalid. Please fix your entries and re-run the target:
[ERROR] [security.ldap.domain = null] 'security.ldap.domain' property is not defined.
[WARN ] There's a warning about one or more properties. Please review messages below and re-run the target if needed:
[WARN ] [ldap.url = ldap://152.144.227.88:389, security.ldap.domain = null] Unable to find users directory in LDAP domain.
[INFO ] Upfront validation of 'security' bundle for 'single' node type was unsuccessful
[INFO ] Validation was unsuccessful.

Cause

This could be caused due to value of 'security.ldap.domain' not correctly set in deploy.properties file.

Resolution

UPDATED: March 7, 2018
Set 'security.ldap.domain' field in deploy.properties file, reinstall the EngageOne Server 4.X security bundle and validate.