Mercurial > prosody-modules
view mod_muc_auto_reserve_nicks/mod_muc_auto_reserve_nicks.lua @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +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);