Mercurial > prosody-modules
view mod_discodot/mod_discodot.tl @ 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 | 253df0798996 |
children |
line wrap: on
line source
local cm = require"core.configmanager"; local function format_host(host:string, conf:{string:any}) : string if host == "*" then return "Global"; end local component_module = conf["component_module"]; if component_module is string then if component_module == "component" then return string.format("Component %q", host); else return string.format("Component %q %q", host, component_module); end else return string.format("VirtualHost %q", host); end end function module.command(arg : { string }) : integer local config : { string : { string : any } } = cm.getconfig(); print"digraph \"prosody\" {" for host, conf in pairs(config) do print(string.format("%q [label=%q]", host, format_host(host, conf))); local parent = host:match("%.(.*)"); if parent and rawget(config, parent) then print(string.format("%q -> %q", parent, host)); end local disco_items = conf["disco_items"] if disco_items is { { string, string } } then for _, pair in ipairs(disco_items) do print(string.format("%q -> %q", host, pair[1])); end end end print"}" return 0 end