Mercurial > prosody-modules
view mod_log_sasl_mech/mod_log_sasl_mech.lua @ 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 | 4baaa5a66a5a |
children | 5ff8022466ab |
line wrap: on
line source
module:hook("authentication-success", function (event) local session = event.session; local sasl_handler = session.sasl_handler; session.log("info", "Authenticated with %s", sasl_handler and sasl_handler.selected or "legacy auth"); end);