Mercurial > prosody-modules
view mod_stats39/mod_stats39.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 | bac3dae031ee |
children |
line wrap: on
line source
local statsman = require "core.statsmanager"; local st = require "util.stanza"; local s_format = string.format; assert(statsman.get_stats, "not compatible with trunk based on openmetrics"); module:add_feature("http://jabber.org/protocol/stats"); module:hook("iq/host/http://jabber.org/protocol/stats:query", function (event) local origin, stanza = event.origin, event.stanza; local stats, _, extra = statsman.get_stats(); local reply = st.reply(stanza); reply:tag("query", { xmlns = "http://jabber.org/protocol/stats" }); for stat, value in pairs(stats) do local unit = extra[stat] and extra[stat].units; reply:tag("stat", { name = stat, unit = unit, value = s_format("%.12g", value) }):up(); end origin.send(reply); return true; end)