Mercurial > prosody-modules
view mod_muc_auto_reserve_nicks/mod_muc_auto_reserve_nicks.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 | c83bc703825d |
children |
line wrap: on
line source
local jid = require "util.jid"; local set = require "util.set"; local active_affiliations = set.new({ "member", "admin", "owner" }); module:hook("muc-occupant-joined", function (event) local room, occupant = event.room, event.occupant; local user_jid = occupant.bare_jid; local user_affiliation = room:get_affiliation(user_jid); if not active_affiliations:contains(user_affiliation) then return; end local aff_data = event.room:get_affiliation_data(user_jid); if not aff_data then local reserved_nick = jid.resource(occupant.nick); module:log("debug", "Automatically reserving nickname '%s' for <%s>", reserved_nick, user_jid); room:set_affiliation_data(user_jid, "reserved_nickname", reserved_nick); room._reserved_nicks = nil; -- force refresh of nickname map end end);