Software /
code /
prosody-modules
File
mod_extdisco/README.markdown @ 5705: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 |
parent | 4020:4b47c8eeca22 |
line wrap: on
line source
--- summary: External Service Discovery ... Introduction ============ This module adds support for [XEP-0215: External Service Discovery], which lets Prosody advertise non-XMPP services. Configuration ============= Example services from the XEP: ``` {.lua} modules_enabled = { -- other modules ... "extdisco"; } external_services = { ["stun.shakespeare.lit"] = { port="9998"; transport="udp"; type="stun"; }; ["relay.shakespeare.lit"] = { password="jj929jkj5sadjfj93v3n"; port="9999"; transport="udp"; type="turn"; username="nb78932lkjlskjfdb7g8"; }; ["192.0.2.1"] = { port="8888"; transport="udp"; type="stun"; }; ["192.0.2.1"] = { port="8889"; password="93jn3bakj9s832lrjbbz"; transport="udp"; type="turn"; username="auu98sjl2wk3e9fjdsl7"; }; ["ftp.shakespeare.lit"] = { name="Shakespearean File Server"; password="guest"; port="20"; transport="tcp"; type="ftp"; username="guest"; }; } ``` Compatibility ============= Incompatible with [mod_turncredentials](https://modules.prosody.im/mod_turncredentials).