Mercurial > prosody-modules
view mod_discoitems/mod_discoitems.lua @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | ae91c98b7e4c |
children |
line wrap: on
line source
-- mod_discoitems.lua -- -- In the config, you can add: -- -- disco_items = { -- {"proxy.eu.jabber.org", "Jabber.org SOCKS5 service"}; -- {"conference.jabber.org", "The Jabber.org MUC"}; -- }; -- local st = require "util.stanza"; local result_query = st.stanza("query", {xmlns="http://jabber.org/protocol/disco#items"}); for _, item in ipairs(module:get_option("disco_items") or {}) do result_query:tag("item", {jid=item[1], name=item[2]}):up(); end module:hook('iq/host/http://jabber.org/protocol/disco#items:query', function(event) local stanza = event.stanza; local query = stanza.tags[1]; if stanza.attr.type == 'get' and not query.attr.node then event.origin.send(st.reply(stanza):add_child(result_query)); return true; end end, 100);