Mercurial > prosody-modules
view mod_measure_muc/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 | 39931d727c22 |
| children |
line wrap: on
line source
--- labels: - Statistics summary: Collect statistics on Grout Chat ... Description =========== This module collects statistics from group chat component. It collects current count of hidden, persistent, archive-enabled, password protected rooms. The current count of room is also exposed (hidden+public). Configuration ============= mod\_measure\_muc must be load on MUC components (not globally): ```lua Component "conference.example.com" "muc" modules_enabled = { "measure_muc"; } ``` See also the documentation of Prosody’s [MUC module](https://prosody.im/doc/modules/mod_muc). Compatibility ============= ------- ------------- trunk Works 0.11 Works 0.10 Unknown 0.9 Does not work ------- -------------