Mercurial > prosody-modules
view mod_muc_config_restrict/mod_muc_config_restrict.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 | ed7431fd3b47 |
children |
line wrap: on
line source
local is_admin = require "core.usermanager".is_admin; local t_remove = table.remove; local restricted_options = module:get_option_set("muc_config_restricted", {})._items; function handle_config_submit(event) local stanza = event.stanza; if is_admin(stanza.attr.from, module.host) then return; end -- Don't restrict admins local fields = event.fields; for option in restricted_options do fields[option] = nil; -- Like it was never there end end function handle_config_request(event) if is_admin(event.actor, module.host) then return; end -- Don't restrict admins local form = event.form; for i = #form, 1, -1 do if restricted_options[form[i].name] then t_remove(form, i); end end end module:hook("muc-config-submitted", handle_config_submit); module:hook("muc-config-form", handle_config_request);