Mercurial > prosody-modules
view mod_muc_auto_member/README.markdown @ 5796:93d6e9026c1b
mod_http_oauth2: Do not enforce PKCE on Device and OOB flows
PKCE does not appear to be used with the Device flow. I have found no
mention of any interaction between those standards. Since no data is
delivered via redirects in these cases, PKCE may not serve any purpose.
This is mostly a problem because we reuse the authorization code to
implement the Device and OOB flows.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 15 Dec 2023 12:10:07 +0100 |
parents | 243c156074d3 |
children |
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.