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.

-- Compatibility with clients that set 'to' on resource bind requests
--
-- http://xmpp.org/rfcs/rfc3920.html#bind
-- http://xmpp.org/rfcs/rfc6120.html#bind-servergen-success

local st = require "util.stanza";

module:hook("iq/host/urn:ietf:params:xml:ns:xmpp-bind:bind", function(event)
	local fixed_stanza = st.clone(event.stanza);
	fixed_stanza.attr.to = nil;
	prosody.core_process_stanza(event.origin, fixed_stanza);
	return true;
end);