Summary

Question

Answer

The entirety of Palamida?s LDAP configuration is done through the $palamida/config/core/core.ldap.properties file. The file is self-documenting with comments explaining each property.

Below are the main properties which need to be set:

ldap.enabled

This property enables LDAP-based authentication to the Palamida application.

ldap.user.sync.enabled

This property enables syncing of Palamida users from the LDAP server (i.e., pulling in users from LDAP into the Palamida application).

ldap.url

The hostname of the LDAP server, followed by a port number (389 for LDAP, 636 for LDAPS).

Example: ldap://myadserver.corp.com:389

ldap.username
ldap.password

These need to be set to the appropriate credentials to log in and query the LDAP server.

ldap.base
ldap.searchbase

This is somewhat of a tricky combination that seems to depend on the organization?s LDAP tree set-up. The important thing to remember is to NOT append ldap.base to ldap.searchbase.

Basically, ldap.base is the base node of all the necessary information to be searched in your LDAP server, while the ldap.searchBase is the base node for the users specifically.

Palamida ships the example file with ?ldap.base = dc=adtest,dc=palamida,dc=com? and ?ldap.searchBase = CN=Users?. Based on the properties we ship our file with, our LDAP tree thus looks like this:

Make sure that the attributes of your ldap.base node do not also appear in the attributes of your ldap.searchBase node, because the LDAP connector will try to append ldap.base to ldap.searchBase automatically, so that although ?ldap.searchBase = CN=Users? appears in the properties file, Palamida understands the full attributes of the ldap.searchBase node are actually combined with ldap.base as ?CN=Users,DC=adtest,DC=palamida,DC=com?

ldap.searchFilter

This is where the query/search filter go. Your organization should have this prepared, so if you don?t have it, contact your LDAP administrator. Otherwise, you'll need to create an appropriate one using an LDAP client.

It is helpful to have a tool to query your LDAP server to test search filters and connection settings without Palamida, such as JXplorer (http://jxplorer.org/). There are other clients available as well, both graphical and command-line.

ldap.jobFrequency

This property is used to set the LDAP import frequency/timing. The default value in the properties file is:

ldap.jobFrequency=0 0 6 * * ?

This means that every morning at 6 AM the system syncs up with the LDAP server.

Another LDAP frequency example syntax is as follows:

ldap.jobFrequency=0 0/1 * * * ?

This means that Palamida syncs once a minute with the LDAP server.

Refer to this site for further information about the Quartz/cron expression format.

Additional Information

Example: ldap://myadserver.corp.com:389