Mercurial > prosody-modules
view mod_muc_defaults/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | 22784f001b7f |
children | a1f8cc591b66 |
line wrap: on
line source
# mod_muc_defaults Creates MUCs with default configuration settings upon Prosody startup. ## Configuration Under your MUC component, add a `muc_defaults` option with the relevant settings. ``` Component "conference.example.org" "muc" modules_enabled = { "muc_defaults"; } muc_defaults = { { jid_node = "trollbox", affiliations = { admin = { "admin@example.org", "superuser@example.org" }, owner = { "owner@example.org" }, visitors = { "visitor@example.org" } }, config = { name = "General Chat", description = "Public chatroom with no particular topic", allow_member_invites = false, change_subject = false, history_length = 40, lang = "en", logging = true, members_only = false, moderated = false, persistent = true, public = true, public_jids = true } } }; ```