Mercurial > prosody-modules
view mod_auth_imap/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 | b97a2ffef87f |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - 'Type-Auth' summary: IMAP authentication module rockspec: build: modules: mod_auth_imap: auth_imap/mod_auth_imap.lua mod_auth_imap.sasl_imap: auth_imap/sasl_imap.lib.lua ... Introduction ============ This is a Prosody authentication plugin which uses a generic IMAP server as the backend. Configuration ============= option type default --------------------------------- --------- -------------------------------- imap\_auth\_host string localhost imap\_auth\_port number nil imap\_auth\_realm string Same as the sasl\_realm option imap\_auth\_service\_name string nil auth\_append\_host boolean false auth\_imap\_verify\_certificate boolean true auth\_imap\_ssl table A SSL/TLS config