Mercurial > prosody-modules
view mod_muc_defaults/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 | a1f8cc591b66 |
children |
line wrap: on
line source
# mod_muc_defaults Creates MUCs with default configuration settings upon Prosody startup. ## Configuration Under your MUC component, add a `default_mucs` option with the relevant settings. ``` Component "conference.example.org" "muc" modules_enabled = { "muc_defaults"; } default_mucs = { { 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 } } }; ```