Mercurial > prosody-modules
view mod_muc_local_only/mod_muc_local_only.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 | 221b6bee26e2 |
| children |
line wrap: on
line source
local jid = require "util.jid"; local st = require "util.stanza"; local local_rooms = module:get_option_inherited_set("muc_local_only", {}); module:hook("muc-occupant-pre-join", function (event) local room = event.room; if not local_rooms:contains(room.jid) then return; -- Not a protected room, ignore end local user_jid = event.occupant.bare_jid; local user_host = jid.host(user_jid); if not prosody.hosts[user_host] then local error_reply = st.error_reply(event.stanza, "cancel", "forbidden", "This group is only available to local users", room.jid); event.origin.send(error_reply); return true; end room:set_affiliation(true, user_jid, "member", "Granting access to local user"); end);
