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 jid_split = require "util.jid".split;
local jid_bare = require "util.jid".bare;
local load_roster = require "core.rostermanager".load_roster;

local blocked_servers = module:get_option_set("block_s2s_subscriptions")._items;

function filter_presence(event)
	if blocked_servers[event.origin.from_host] and event.stanza.attr.type == "subscribe" then
		local stanza = event.stanza;
		local to_user, to_host = jid_split(stanza.attr.to);
		local roster = load_roster(to_user, to_host);
		if roster and roster[jid_bare(stanza.attr.from)] then
			return; -- In roster, pass through
		end
		return true; -- Drop
	end
end

module:hook("presence/bare", filter_presence, 200); -- Client receiving