Mercurial > prosody-modules
view mod_vjud/README.markdown @ 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 | 0aee099f270d |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'XEP-0055: Jabber Search' ... Introduction ============ Basic implementation of [XEP-0055: Jabber Search]. Details ======= This module has two modes. One mode requires users to opt-in to be searchable, then allows users to search the list of those users. The second mode allows search across all users. Usage ===== First copy the module to the prosody plugins directory. Then add "vjud" to your modules\_enabled list: modules_enabled = { -- ... "vjud", -- ... } Alternatively, you can load it as a component: Component "search.example.com" "vjud" (Some old clients require this) Configuration ============= Option Default Description ------------ ---------- -------------------------------- vjud\_mode "opt-in" Choose how users are listed in the directory ("opt-in" or "all") Compatibility ============= ------- --------------------------------- 0.8 Works, but only the opt-in mode 0.9 Works trunk Works ------- --------------------------------- Note that the version for 0.8 and 0.9 are slightly different.