Mercurial > prosody-modules
view mod_http_user_count/mod_http_user_count.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 | a45f2f79e99b |
children |
line wrap: on
line source
local it = require "util.iterators"; local jid_split = require "util.jid".prepped_split; module:depends("http"); local function check_muc(jid) local room_name, host = jid_split(jid); if not hosts[host] then return nil, "No such host: "..host; elseif not hosts[host].modules.muc then return nil, "Host '"..host.."' is not a MUC service"; end return room_name, host; end module:provides("http", { route = { ["GET /sessions"] = function () return tostring(it.count(it.keys(prosody.full_sessions))); end; ["GET /users"] = function () return tostring(it.count(it.keys(prosody.bare_sessions))); end; ["GET /host"] = function () return tostring(it.count(it.keys(prosody.hosts[module.host].sessions))); end; ["GET /room/*"] = function (request, room_jid) local name, host = check_muc(room_jid); if not name then return "0"; end local room = prosody.hosts[host].modules.muc.rooms[name.."@"..host]; if not room then return "0"; end return tostring(it.count(it.keys(room._occupants))); end; }; });