Mercurial > prosody-modules
view mod_measure_client_features/mod_measure_client_features.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 | 5fdbf416bd40 |
children |
line wrap: on
line source
module:set_global(); local measure = require"core.statsmanager".measure; local disco_ns = "http://jabber.org/protocol/disco#info"; local counters = { total = measure("amount", "client_features.total"); }; module:hook("stats-update", function () local total = 0; local buckets = {}; for _, session in pairs(prosody.full_sessions) do local disco_info = session.caps_cache; if disco_info ~= nil then for feature in disco_info:childtags("feature", disco_ns) do local var = feature.attr.var; if var ~= nil then if buckets[var] == nil then buckets[var] = 0; end buckets[var] = buckets[var] + 1; end end total = total + 1; end end for bucket, count in pairs(buckets) do if counters[bucket] == nil then counters[bucket] = measure("amount", "client_features."..bucket); end counters[bucket](count); end counters.total(total); end)