view mod_muc_auto_reserve_nicks/mod_muc_auto_reserve_nicks.lua @ 5285:8e1f1eb00b58

mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.
author Matthew Wild <mwild1@gmail.com>
date Wed, 29 Mar 2023 16:12:15 +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);