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.

module:set_global()

local custom_metric = require "core.statsmanager".metric
local gc_bytes = custom_metric(
	"gauge", "lua_heap", "bytes",
	"Memory used by objects under control of the Lua garbage collector"
):with_labels()

module:hook("stats-update", function ()
	local kbytes = collectgarbage("count");
  gc_bytes:set(kbytes * 1024);
end);

custom_metric("gauge", "lua_info", "", "Lua runtime version", { "version" }):with_labels(_VERSION):set(1);