Modules/1.2/sqlauth
From the makers of InspIRCd.
sqlauth module (InspIRCd-1.2 version)
| 1.0 Documentation | 1.1 Documentation | 1.2 Documentation |
| Description
|
| This module allows you to allow and deny connections to your irc servers using a backend database, and is customizable to work with the majority of popular web based software. If software has both a username and a password field in one of its tables, it is likely to work with this module. |
| Configuration Tags
| ||||||||||||||
<sqlauth dbid="1"
query="SELECT username FROM testusers WHERE username='$nick' AND password='$md5pass' LIMIT 1"
killreason="Access denied"
allowpattern="Guest*"
verbose="1">
The variables in the tag have the following meanings:
For a list of settings which are known to work with certain popular software, please see our Integrating m_sqlauth.so with other software page.
<tr><td>$ident</td><td>This is replaced with the user's ident (username) string. Do not use the m_ident module if you use this variable to authenticate users, otherwise you will be unable to determine if you are checking the ident string returned by the user's ident server, or the one sent by the USER command.</td></tr></table> <tr><td>$gecos</td><td>This is replaced with the user's GECOS (Real name).</td></tr></table> <tr><td>$server</td><td>This is replaced with name of the server the user connected to.</td></tr></table> <tr><td>$uuid</td><td>This is replaced with the user's UUID. This is of limited and specialist use as the user's UUID changes upon every connection.</td></tr></table> |
| Modes
|
| This module does not implement any extra user or channel modes. |
| Extended Bans (Extbans)
|
| This module implements no extended bans. |
| Commands
|
| This module adds no extra commands. |
| Special Notes
|
This module will check the user's nickname against the user field, and their password against the password field. The password is collected using the RFC 1459 notation, e.g.
PASS :password The user will not be prompted for their password, if this is not clear enough to your users, you should place it into the kill message. It is highly recommended that if you are using a system such as this, you should disable nick changing once users are connected with the following syntax in your configuration file: <disabled commands="NICK"> With such a setting in place, you can be sure that everyone who connects is registered, and they cannot possibly impersonate others. Beware of mixing this system with other systems which may force user nickchanges. If a users nick is changed when such a system is in place, they will be unable to change it back without reconnecting! |
| This module is an 'extra' module. This means that by default it is not compiled when you type make to build your IRCd. To enable this module follow these steps. |
| Dependencies
|
|

















