Mercurial > prosody-modules
view mod_secure_interfaces/mod_secure_interfaces.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 | 6c806a99f802 |
children |
line wrap: on
line source
local secure_interfaces = module:get_option_set("secure_interfaces", { "127.0.0.1", "::1" }); module:hook("stream-features", function (event) local session = event.origin; if session.type ~= "c2s_unauthed" then return; end local socket = session.conn:socket(); if not socket.getsockname then module:log("debug", "Unable to determine local address of incoming connection"); return; end local localip = socket:getsockname(); if secure_interfaces:contains(localip) then module:log("debug", "Marking session from %s to %s as secure", session.ip or "[?]", localip); session.secure = true; session.conn.starttls = false; else module:log("debug", "Not marking session from %s to %s as secure", session.ip or "[?]", localip); end end, 2500);