Mercurial > prosody-modules
view mod_storage_ejabberdsql_readonly/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 | 9754eedbc4d1 |
| children |
line wrap: on
line source
--- labels: - 'Type-Storage' - 'Stage-Alpha' summary: Ejabberd SQL Read-only Storage Module ... Introduction ============ This is a storage backend using Ejabberd’s SQL backend. It depends on [LuaDBI][doc:depends#luadbi] This module only works in read-only, and was made to be used by [mod_migrate] to migrate from Ejabberd’s SQL backend. Configuration ============= Copy the module to the prosody modules/plugins directory. In Prosody's configuration file, set: storage = "ejabberdsql_readonly" EjabberdSQL options are the same as the [SQL ones][doc:modules:mod_storage_sql#usage]. Compatibility ============= ------- --------------------------- trunk Works 0.10 Untested, but should work 0.9 Does not work ------- ---------------------------