view mod_muc_lang/mod_muc_lang.lua @ 5682:527c747711f3

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.
author Kim Alvefur <zash@zash.se>
date Sun, 29 Oct 2023 11:30:49 +0100
parents ef5d52ca31bb
children
line wrap: on
line source

assert(module:depends"muc".rooms, "This module is not required with Prosody >= 0.11");

module:hook("muc-config-form", function(event)
	local room, form = event.room, event.form;
	table.insert(form, {
		name = "muc#roomconfig_lang",
		type = "text-single",
		label = "Natural Language for Room Discussions",
		value = room._data.language,
	});
end);

module:hook("muc-config-submitted", function(event)
	local room, fields, changed = event.room, event.fields, event.changed;
	local new = fields["muc#roomconfig_lang"];
	if new ~= room._data.language then
		room._data.language = new;
		if type(changed) == "table" then
			changed["muc#roomconfig_lang"] = true;
		else
			event.changed = true;
		end
	end
end);

module:hook("muc-disco#info", function (event)
	local room, form, formdata = event.room, event.form, event.formdata;

	table.insert(form, {
		name = "muc#roominfo_lang",
		value = room._data.language,
	});
	formdata["muc#roominfo_lang"] = room._data.language;
end);