Software /
code /
prosody-modules
File
mod_auth_sql/README.markdown @ 5378:6155c46d9eea
mod_http_oauth2: Record OAuth software id and version attached to tokens
Unsure if these are used anywhere, but `software_id` is supposedly more
unique than `client_uri` which can vary by registration or something?
Software versions can also be good to know e.g. in case there is a
security issue affecting certain versions that could warrant revocation
of tokens issued to it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 27 Apr 2023 19:16:14 +0200 |
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 ----- -------