Mercurial > prosody-modules
view mod_muc_config_restrict/README.markdown @ 5193:2bb29ece216b
mod_http_oauth2: Implement stateless dynamic client registration
Replaces previous explicit registration that required either the
additional module mod_adhoc_oauth2_client or manually editing the
database. That method was enough to have something to test with, but
would not probably not scale easily.
Dynamic client registration allows creating clients on the fly, which
may be even easier in theory.
In order to not allow basically unauthenticated writes to the database,
we implement a stateless model here.
per_host_key := HMAC(config -> oauth2_registration_key, hostname)
client_id := JWT { client metadata } signed with per_host_key
client_secret := HMAC(per_host_key, client_id)
This should ensure everything we need to know is part of the client_id,
allowing redirects etc to be validated, and the client_secret can be
validated with only the client_id and the per_host_key.
A nonce injected into the client_id JWT should ensure nobody can submit
the same client metadata and retrieve the same client_secret
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Fri, 03 Mar 2023 21:14:19 +0100 |
| parents | 34fb3d239ac1 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Restrict MUC configuration options to server admins ... Introduction ============ Sometimes, especially on public services, you may want to allow people to create their own rooms, but prevent some options from being modified by normal users. For example, using this module you can prevent users from making rooms persistent, or making rooms publicly visible. Details ======= You need to supply a list of options that will be restricted to admins. Available options can vary, but the following table lists Prosody's built-in options (as defined in XEP-0045): Name Description --------------------------------- ------------------------------------------- muc\#roomconfig\_roomname The title/name of the room muc\#roomconfig\_roomdesc The description of the room muc\#roomconfig\_persistentroom Whether the room should remain when empty muc\#roomconfig\_publicroom Whether the room is publicly visible muc\#roomconfig\_changesubject Whether occupants can change the subject muc\#roomconfig\_whois Control who can see occupant's real JIDs muc\#roomconfig\_roomsecret The room password muc\#roomconfig\_moderatedroom Whether the room is moderated muc\#roomconfig\_membersonly Whether the room is members-only muc\#roomconfig\_historylength The length of the room history Some plugins may add other options to the room config (in Prosody 0.10+), for which you will need to consult their documentation for the full option name. Configuration ============= Enable the plugin on a MUC host (do not put it in your global modules\_enabled list): ``` {.lua} Component "conference.example.com" "muc" modules_enabled = { "muc_config_restrict" } muc_config_restricted = { "muc#roomconfig_persistentroom"; -- Prevent non-admins from changing a room's persistence setting "muc#roomconfig_membersonly"; -- Prevent non-admins from changing whether rooms are members-only } ``` Compatibility ============= ------- -------------- trunk Doesn't work (uses is_admin) 0.12 Works? ------- --------------