Mercurial > prosody-modules
view mod_groups_shell/mod_groups_shell.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 | 8b69e0b56db2 |
children |
line wrap: on
line source
module:set_global() local modulemanager = require "core.modulemanager"; local shell_env = module:shared("/*/admin_shell/env") shell_env.groups = {}; function shell_env.groups:sync_group(host, group_id) local print = self.session.print; if not host then return false, "host not given" end local mod_groups = modulemanager.get_module(host, "groups_internal") if not mod_groups then return false, host .. " does not have mod_groups_internal loaded" end if not group_id then return false, "group id not given" end local ok, err = mod_groups.emit_member_events(group_id) if ok then return true, "Synchronised members" else return ok, err end end