Mercurial > prosody-modules
view mod_admin_blocklist/README.markdown @ 5447:aa4828f040c5
mod_http_oauth2: Enforce client scope restrictions in authorization
When registering a client, a scope field can be included as a promise to
only ever use those. Here we enforce that promise, if given, ensuring a
client can't request or be granted a scope it didn't provide in its
registration. While currently there is no restrictions at registration
time, this could be changed in the future in various ways.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Thu, 11 May 2023 19:33:44 +0200 |
| parents | 96e83b4a93f7 |
| children |
line wrap: on
line source
--- summary: Block s2s connections based on admin blocklists ... This module uses the blocklists set by admins for blocking s2s connections. So if an admin blocks a bare domain using [Blocking Command][xep191] via [mod\_blocklist][doc:modules:mod_blocklist] then no s2s connections will be allowed to or from that domain. # Configuring ## Prosody 0.12 Starting with Prosody 0.12, the role or roles that determine whether a particular users blocklist is used can be configured: ```lua -- This is the default: admin_blocklist_roles = { "prosody:operator", "prosody:admin" } ``` ## Prosody 0.11 In Prosody 0.11 the [`admins`][doc:admins] setting is used.