view mod_measure_stanza_counts/mod_measure_stanza_counts.lua @ 5682:527c747711f3

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.
author Kim Alvefur <zash@zash.se>
date Sun, 29 Oct 2023 11:30:49 +0100
parents 33b1b6ff23d8
children
line wrap: on
line source

module:set_global()

local filters = require"util.filters";

local stanzas_in = module:metric(
	"counter", "received", "",
	"Stanzas received by Prosody",
	{ "session_type", "stanza_kind" }
)
local stanzas_out = module:metric(
	"counter", "sent", "",
	"Stanzas sent by prosody",
	{ "session_type", "stanza_kind" }
)

local stanza_kinds = { message = true, presence = true, iq = true };

local function rate(metric_family)
	return function (stanza, session)
		if stanza.attr and not stanza.attr.xmlns and stanza_kinds[stanza.name] then
			metric_family:with_labels(session.type, stanza.name):add(1);
		end
		return stanza;
	end
end

local function measure_stanza_counts(session)
	filters.add_filter(session, "stanzas/in",  rate(stanzas_in));
	filters.add_filter(session, "stanzas/out", rate(stanzas_out));
end

filters.add_filter_hook(measure_stanza_counts);