Indeed, any <ahref="http://search.cpan.org/search?query=DBD%3A%3A&mode=module"class="urlextern"title="http://search.cpan.org/search?query=DBD%3A%3A&mode=module"rel="nofollow">Perl DBD driver</a> can be used.
</p>
</div>
<!-- EDIT4 SECTION "Drivers" [123-371] -->
<h3class="sectionedit5"id="schema">Schema</h3>
<divclass="level3">
<p>
<abbrtitle="LemonLDAP::NG">LL::NG</abbr> can use two tables:
</p>
<ul>
<liclass="level1"><divclass="li"> Authentication table: where login and password are stored</div>
</li>
<liclass="level1"><divclass="li"> User table: where user data are stored (mail, name, etc.)</div>
</li>
</ul>
<divclass="notetip">Authentication table and user table can be the same.
</div>
<p>
The password can be in plain text, or encoded with a standard SQL method:
</p>
<ul>
<liclass="level1"><divclass="li"> SHA</div>
</li>
<liclass="level1"><divclass="li"> SHA1</div>
</li>
<liclass="level1"><divclass="li"> MD5</div>
</li>
</ul>
</div>
<h4id="example_1two_tables">Example 1: two tables</h4>
In Manager, go in <code>General Parameters</code>><code>Authentication modules</code> and choose Database (<abbrtitle="Database Interface">DBI</abbr>) for authentication, users and/or password modules.
The authentication level given to users authenticated with this module.
</p>
<divclass="noteimportant">As <abbrtitle="Database Interface">DBI</abbr> is a login/password based module, the authentication level can be:<ul>
<liclass="level1"><divclass="li"> increased (+1) if portal is protected by SSL (HTTPS)</div>
</li>
<liclass="level1"><divclass="li"> decreased (-1) if the portal autocompletion is allowed (see <ahref="portalcustom.html"class="wikilink1"title="documentation:2.0:portalcustom">portal customization</a>)</div>
List of columns to query to fill user session. See also <ahref="exportedvars.html"class="wikilink1"title="documentation:2.0:exportedvars">exported variables configuration</a>.
<divclass="notetip">Connection settings can be configured differently for authentication process and user process. This allows one to use different databases for these process. By default, if user process connection settings are empty, authentication process connection settings will be used.
<liclass="level1"><divclass="li"><strong>Chain</strong>: <abbrtitle="Database Interface">DBI</abbr> chain, including database driver name and database name (for example: dbi:mysql:database=lemonldapng;host=localhost).</div>
<liclass="level1"><divclass="li"><strong>Dynamic hash activation</strong>: Activate dynamic hashing. With dynamic hashing, the hash scheme is recovered from the user password in the database during authentication.</div>
</li>
<liclass="level1"><divclass="li"><strong>Supported non-salted schemes</strong>: List of whitespace separated hash schemes. Every hash scheme MUST match a non-salted hash function in the database. LemonLDAP::NG relies on this hashing function for computing user password hashes. These hashes MUST NOT be salted (no random data used in conjunction with the password).</div>
</li>
<liclass="level1"><divclass="li"><strong>Supported salted schemes</strong>: List of whitespace separated salted hash schemes, of the form “<strong>s</strong>scheme”, where scheme MUST match a non-salted hash function in the database. LemonLDAP::NG relies on this hashing function for computing user password hashes. Salted and non-salted scheme lists are not necessarily equivalent. (for example: non-salted=“sha256” and salted=“ssha ssha512” is valid)</div>
</li>
<liclass="level1"><divclass="li"><strong>Dynamic hash scheme for new passwords</strong>: LemonLDAP::NG is able to store new passwords in the database (while modifying or reinitializing the password). You can choose a salted or non salted dynamic hashed password. The value must be an element of “Supported non-salted schemes” or “Supported salted schemes”.</div>