Software /
code /
prosody-modules
File
mod_auth_sql/README.markdown @ 5218:1f4b768c831a
mod_http_oauth2: Correct field name for HTTP response status code
'code' is used in the incoming side of the Prosody HTTP stack while
'status_code' is used on the response side. Not confusing at all.
The default is 200 so this mistake had no real effect.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 07 Mar 2023 13:14:25 +0100 |
parent | 1803:4d73a1a6ba68 |
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. Compatibility ============= ----- ------- 0.8 Works ----- -------