Mercurial > prosody-modules
view mod_nooffline_noerror/mod_nooffline_noerror.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 | e0f3e29ab18a |
| children |
line wrap: on
line source
-- Ignore disabled offline storage -- -- Copyright (C) 2019-2020 Thilo Molitor -- -- This project is MIT/X11 licensed. Please see the -- COPYING file in the source package for more information. -- -- depend on mod_mam to make sure mam is at least loaded and active module:depends "mam"; -- ignore offline messages and don't return any error (the message will be already in MAM at this point) -- this is *only* triggered if mod_offline is *not* loaded and completely ignored otherwise module:hook("message/offline/handle", function(event) local log = event.origin and event.origin.log or module._log; if log then log("info", "Ignoring offline message (mod_offline seems *not* to be loaded)..."); end return true; end, -100);