prosody-modules
527c747711f3
mod_muc_auto_member/README.markdown
Software / code / prosody-modules
File
mod_muc_auto_member/README.markdown @ 5705: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 |
| parent | 5162:243c156074d3 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: "Automatically register new MUC participants as members" ... # Introduction This module automatically makes anybody who joins a MUC become a registered member. This can be useful for certain use cases. Note: there is no automatic cleanup of members. If you enable this on a server with busy public channels, your member list will perpetually increase in size. Also, there is currently no per-room option for this behaviour. That may be added in the future, along with membership expiry. # Configuration There is currently no configuration for this module. The module should be enabled on your MUC component, i.e. in the modules_enabled option under your Component: ``` {.lua} Component "conference.example.com" "muc" modules_enabled = { "muc_auto_member"; } ``` # Compatibility 0.12 and later.
