Mercurial > prosody-modules
view mod_tlsfail/mod_tlsfail.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 | 7009e16192fa |
children |
line wrap: on
line source
local st = require "util.stanza"; local xmlns_starttls = 'urn:ietf:params:xml:ns:xmpp-tls'; local starttls_attr = { xmlns = xmlns_starttls }; local s2s_feature = st.stanza("starttls", starttls_attr); local starttls_failure = st.stanza("failure", starttls_attr); module:hook("stream-features", function(event) local features = event.features; features:add_child(s2s_feature); end); module:hook("s2s-stream-features", function(event) local features = event.features; features:add_child(s2s_feature); end); -- Hook <starttls/> module:hook("stanza/urn:ietf:params:xml:ns:xmpp-tls:starttls", function(event) local origin = event.origin; (origin.sends2s or origin.send)(starttls_failure); origin:close(); return true; end);