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.

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);