Databases

Authentication Users Password
✔ ✔ ✔

Presentation

Drivers

LL::NG can use a lot of databases as authentication, users and password backend:

Indeed, any Perl DBD driver can be used.

Schema

LL::NG can use two tables:

Authentication table and user table can be the same.

The password can be in plain text, or encoded with a standard SQL method:

Example 1: two tables

Authentication table
id login password
0 coudot 1f777a6581e478499f4284e54fe2d4a4e513dfff
1 xguimard a15a18c8bb17e6f67886a9af1898c018b9f5a072
2 tchemineau 1f777a6581e478499f4284e54fe2d4a4e513dfff
User table
id user name mail
0 coudot Clément OUDOT coudot@example.com
1 tchemineau Thomas CHEMINEAU tchemineau@example.com
2 xguimard Xavier GUIMARD xguimard@example.com

Example 2: single table

id user password name mail
0 coudot 1f777a6581e478499f4284e54fe2d4a4e513dfff Clément OUDOT coudot@example.com
1 tchemineau 1f777a6581e478499f4284e54fe2d4a4e513dfff Thomas CHEMINEAU tchemineau@example.com
2 xguimard a15a18c8bb17e6f67886a9af1898c018b9f5a072 Xavier GUIMARD xguimard@example.com

SQL

LL::NG will operate some SQL queries:

Configuration

In Manager, go in General Parameters > Authentication modules and choose Database (DBI) for authentication, users and/or password modules.

Authentication level

The authentication level given to users authenticated with this module.

As DBI is a login/password based module, the authentication level can be:

  • increased (+1) if portal is protected by SSL (HTTPS)
  • decreased (-1) if the portal autocompletion is allowed (see portal customization)

Exported variables

List of columns to query to fill user session. See also exported variables configuration.

Connection

Connection settings can be configured differently for authentication process and user process. This allows to use different databases for these process. By default, if user process connection settings are empty, authentication process connection settings will be used.

Schema

Password