view mod_proxy65_whitelist/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 8de50be756e5
children 694b62d8a82f
line wrap: on
line source

---
labels: 'Stage-Alpha'
summary: Limit which file transfer users can use
...

Introduction
------------

This module attempts to restrict use of non-whitelisted XEP-0065
proxies.

Configuration
-------------

Without any options, the module will restrict users to local [proxy65
components](https://prosody.im/doc/modules/mod_proxy65).

    -- additional proxies to allow
    allowed_streamhosts = { "proxy.eu.jabber.org" }

The module will add all local proxies to that list. To prevent it from
doing that, set

    allow_local_streamhosts = false