Mercurial > prosody-modules
view mod_muc_local_only/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 | 221b6bee26e2 |
children |
line wrap: on
line source
# Introduction This module allows you to make one or more MUCs as accessible to local users only. # Details Local users (anyone on the same server as the MUC) are granted automatic membership when they first join the room. Users from other servers are denied access (even if the room is otherwise configured to be open). # Configuring ## Enabling ``` {.lua} Component "rooms.example.net" "muc" modules_enabled = { "muc_local_only"; } ``` ## Settings Specify a list of MUCs in your config like so: ``` muc_local_only = { "my-local-chat@conference.example.com" } ``` # Compatibility Requires Prosody 0.11.0 or later. # Future It would be good to add a room configuration option.