Mercurial > prosody-modules
view mod_auth_sql/README.markdown @ 5682:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +0100 |
| 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 ----- -------