Mercurial > prosody-modules
view mod_admin_blocklist/README.markdown @ 5271:3a1df3adad0c
mod_http_oauth2: Allow user to decide which requested scopes to grant
These should at the very least be shown to the user, so they can decide
whether to grant them.
Considered whether to filter the requested scopes down to actually
understood scopes that would be granted, but decided that this was a bit
complex for a first step, since role role selection and other kinds of
scopes are mixed into the same field here.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 23 Mar 2023 16:28:08 +0100 |
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.