Mercurial > prosody-modules
view mod_admin_blocklist/README.markdown @ 5425:3b30635d215c
mod_http_oauth2: Support granting zero role-scopes
It seems Very Bad that if you uncheck all roles on the consent page, you
get the default scopes, which seems the opposite of what you probably
intended. Currently, mod_tokenauth will do the same thing, so work is
needed there too to allow issuing tokens without roles.
A token without a role could be used for OIDC login, and not much else.
This seems like a valuable thing to support.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 07 May 2023 19:29:15 +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.