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.

-- mod_offline_hints
--
-- Copyright (C) 2019 Marcos de Vera Piquero <marcos.devera@quobis.com>
--
-- This file is MIT/X11 licensed.
--
-- A module to discard hinted messages with no-store at mod_offline
--

module:depends"offline";

local function handle_offline (event)
	local stanza = event.stanza;
	if (stanza:get_child("no-store", "urn:xmpp:hints") or
		stanza:get_child("no-permanent-store", "urn:xmpp:hints")) then
		module:log("debug", "Not storing offline stanza: %s (urn:xmpp:hints)", stanza);
		return false;
	end
	return nil;
end

module:hook("message/offline/handle", handle_offline);

module:log("debug", "Module loaded");