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.

-- COMPAT for Openfire sending stream headers without to or from.

module:set_global();

module:hook("s2s-check-certificate", function(event)
	local session, host = event.session, event.host;
	if not event.host then
		(session.log or module._log)("warn", "Invalid stream header, certificate will not be trusted")
		session.cert_chain_status = "invalid"
		return true
	end
end, 100);