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.

local jid = require "util.jid";
local st = require "util.stanza";

local local_rooms = module:get_option_inherited_set("muc_local_only", {});

module:hook("muc-occupant-pre-join", function (event)
	local room = event.room;
	if not local_rooms:contains(room.jid) then
		return; -- Not a protected room, ignore
	end
	local user_jid = event.occupant.bare_jid;
	local user_host = jid.host(user_jid);
	if not prosody.hosts[user_host] then
		local error_reply = st.error_reply(event.stanza, "cancel", "forbidden", "This group is only available to local users", room.jid);
		event.origin.send(error_reply);
		return true;
	end
	room:set_affiliation(true, user_jid, "member", "Granting access to local user");
end);