Mercurial > prosody-modules
view mod_readonly/mod_readonly.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 | 7776c9dc5f37 |
children |
line wrap: on
line source
local st = require "util.stanza"; local stores = module:get_option("readonly_stores", { vcard = { "vcard-temp", "vCard" }; }); local namespaces = {}; for name, namespace in pairs(stores) do namespaces[table.concat(namespace, ":")] = name; end local function prevent_write(event) local stanza = event.stanza; local xmlns_and_tag = stanza.tags[1].attr.xmlns..":"..stanza.tags[1].name; local store_name = namespaces[xmlns_and_tag]; if store_name then module:log("warn", "Preventing modification of %s store by %s", store_name, stanza.attr.from); event.origin.send(st.error_reply(stanza, "cancel", "not-allowed", store_name.." data is read-only")); return true; -- Block stanza end end for namespace in pairs(namespaces) do module:hook("iq-set/bare/"..namespace, prevent_write, 200); end