<liclass="level1"><divclass="li"> Easy to share between servers with remote LDAP access</div>
</li>
<liclass="level1"><divclass="li"> Easy to duplicate with LDAP synchronization services (like SyncRepl in OpenLDAP)</div>
</li>
<liclass="level1"><divclass="li"> Security with SSL/TLS</div>
</li>
<liclass="level1"><divclass="li"> Access control possible by creating one user for Manager (write) and another for portal and handlers (read)</div>
</li>
<liclass="level1"><divclass="li"> Easy import/export through LDIF files</div>
</li>
</ul>
<p>
The configuration will be store under a specific branch, for example <code>ou=conf,ou=applications,dc=example,dc=com</code>.
</p>
<p>
Each configuration will be represented as an entry, which structural objectClass is by default <code>applicationProcess</code>. The configuration name is the same that files, so lmConf-1, lmConf-2, etc. This name is used in entry <abbrtitle="Distinguished Name">DN</abbr>, for example <code>cn=lmConf-1,ou=conf,ou=applications,dc=example,dc=com</code>.
</p>
<p>
Then each parameter is one value of the attribute <code>description</code>, prefixed by its key. For example <code>{ldapPort}389</code>.
Configuration objects use standard object class: <code>applicationProcess</code>. This objectClass allow attributes <code>cn</code> and <code>description</code>. If your LDAP server do not manage this objectClass, configure other objectclass and attributes (see below).
</p>
<p>
We advice to create a specific LDAP account with write access on configuration branch.
</p>
<p>
Next create the configuration branch where you want. Just remember its <abbrtitle="Distinguished Name">DN</abbr> for LemonLDAP::NG configuration.
<liclass="level1"><divclass="li"><strong>ldapServer</strong>: LDAP <abbrtitle="Uniform Resource Identifier">URI</abbr> of the server</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapConfBase</strong>: <abbrtitle="Distinguished Name">DN</abbr> of configuration branch</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapBindDN</strong>: <abbrtitle="Distinguished Name">DN</abbr> used to bind LDAP</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapBindPassword</strong>: password used to bind LDAP</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapObjectClass</strong>: structural objectclass of configuration entry (optional)</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapAttributeId</strong>: RDN attribute of configuration entry (optional)</div>
</li>
<liclass="level1"><divclass="li"><strong>ldapAttributeContent</strong>: attribute used to store configuration values, must be multivalued (optional)</div>