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_statistics_auth
module:set_global();

local auth_ok, auth_fail = 0, 0

function module.add_host(module)
	module:hook("authentication-success", function(event)
		auth_ok = auth_ok + 1
	end);
	module:hook("authentication-failure", function(event)
		auth_fail = auth_fail + 1
	end);
end

module:provides("statistics", {
	statistics = {
		c2s_auth = {
			get = function ()
				return auth_ok;
			end;
			tostring = tostring;
		};
		c2s_authfail = {
			get = function ()
				return auth_fail;
			end;
			tostring = tostring;
		};
	}
});