SQL user database
Sometimes Roxen Challenger needs to access data about the users. The
main reason for this is user authentication, but Roxen can also do
other things with data from the user database, for example, displaying
them on a webpage.
The SQL User Database module enables Roxen Challenger to keep such
user data in an SQL database. The data is stored in a table with the
columns username, passwd, uid, gid,
gecos, homedir and shell. These columns
correspond to the fields in a UNIX password file, and are the fields
that Challenger Authentification modules use. The database must
contain the username and passwd columns, other columns
can be replaced by default values. It is also possible to add extra
columns when needed.
- Cache entries
-
This flag defines whether the module will
cache the database entries or not. Makes accesses faster, but changes
in the database will not show immediately. Recommended.
- Close the database if not used
-
Setting this will save
resources when the module is not used.
- Database close timer
-
How many seconds of inactivity
it should take before the database connection is closed.
- Defaults...
-
- Gecos
-
Default in case there is no gecos column.
- Group ID
-
Default in case there is no gid
column.
- Home Directory
-
Default in case there is no
homedir column.
- Login Shell
-
Default in case there is no shell
column.
- User ID
-
Default in case there is no uid
column. Some modules require the uid to be unique, so it is safer to
acctually store a uid in the database.
- Disable Userlist
-
One of the features of an
authentification module is to get a listing of all users. In the case
of a large user database the call can take a significant amount of
time to process. The feature can therefore be disabled.
- SQL server...
-
The database URL to the database
containing the users.
- Passwords table
-
The name of the table containing the
users.
|