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 mod_groups = module:depends("groups_internal");

module:hook("user-registered", function(event)
	local validated_invite = event.validated_invite or (event.session and event.session.validated_invite);
	if not validated_invite then
		-- not registered via invite, nothing to do
		return
	end
	local groups = validated_invite and validated_invite.additional_data and validated_invite.additional_data.groups;
	if not groups then
		-- invite has no groups, nothing to do
		return
	end

	local new_username = event.username;
	module:log("debug", "adding %s to groups from invite", new_username);
	for _, group in ipairs(groups) do
		mod_groups.add_member(group, new_username);
	end
end);