Mercurial > prosody-modules
view mod_discoitems/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 | 4d73a1a6ba68 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Manually override the list of service discovery items ... Introduction ============ This Prosody plugin lets you manually override the service discovery items for a host. Usage ===== Simply add `"discoitems"` to your modules\_enabled list. Then add the `disco_items` option to hosts for which you wish to override the default response. Note: mod\_disco in Prosody 0.8+ supports the `disco_items` option; this plugin changes the behavior from appending items to replacing items Configuration ============= The `disco_items` option can be added to relevant hosts: disco_items = { {"proxy.eu.jabber.org", "Jabber.org SOCKS5 service"}; {"conference.jabber.org", "The Jabber.org MUC"}; } The format for individual items is `{JID, display-name}`. The display-name can be omitted: `{JID}`. Compatibility ============= ----- ------------- 0.8 Works 0.7 Works 0.6 Works 0.5 Should work ----- -------------