Mercurial > prosody-modules
view mod_auth_sql/README.md @ 6514:668b1f0a4dc6
mod_c2s_limit_sessions: Fix check when it's the first connection
Creation of the sessions[username] entry happens after the
"pre-resource-bind" event, before the "resource-bind" event.
Thus, for a users first connection, it may not exist.
This led to an 'attempt to index a nil value' error, fixed here.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Wed, 08 Apr 2026 15:56:38 +0200 |
| parents | caaa9ea58bec |
| children |
line wrap: on
line source
--- labels: - 'Type-Auth' - 'Stage-Stable' summary: SQL Database authentication module --- Introduction ============ Allow client authentication to be handled by an SQL database query. Unlike mod\_storage\_sql (which is supplied with Prosody) this module allows for custom schemas (though currently it is required to edit the source). Configuration ============= As with all auth modules, there is no need to add this to modules\_enabled. Simply add in the global section, or for the relevant hosts: authentication = "sql" This module reuses the database configuration of [mod\_storage\_sql](http://prosody.im/doc/modules/mod_storage_sql) (the 'sql' option), which you can set even if you are not using SQL as Prosody's primary storage backend. The query is currently hardcoded in the module, so you will need to edit the module to change it. The default query is compatible with jabberd2 DB schema. Database schema =============== `mod_auth_sql` requires a database table `authreg` with the following columns: - `username` - First part of the JID, before the `@` - `realm` - Part of the JID after the `@` - `password` - Plain text password (insecure!) Compatibility ============= ----- ------- 0.8 Works ----- -------
