Mercurial > prosody-modules
view mod_auth_sql/README.markdown @ 5626:a44af1b646f5
mod_http_oauth2: Optionally enforce authentication on revocation endpoint
But why do OAuth require this? If a token leaks, why couldn't anyone
revoke it?
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 31 Jul 2023 02:07:58 +0200 |
parents | 4d73a1a6ba68 |
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. Compatibility ============= ----- ------- 0.8 Works ----- -------