prosody-modules
527c747711f3
mod_s2s_keepalive/README.markdown
Software / code / prosody-modules
File
mod_s2s_keepalive/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 | 3768:bfc4d495bf2c |
line wrap: on
line source
--- summary: Keepalive s2s connections ... Introduction ============ This module periodically sends [XEP-0199] ping requests to remote servers to keep your connection alive. Configuration ============= Simply add the module to the `modules_enabled` list like any other module. By default, all current s2s connections will be pinged periodically. To ping only a subset of servers, list these in `keepalive_servers`. The ping interval can be set using `keepalive_interval`. If no response to the ping has been received in about 10 minutes (or `keepalive_timeout` seconds) the s2s connections are closed. ``` lua modules_enabled = { ... "s2s_keepalive" } keepalive_servers = { "conference.prosody.im"; "rooms.swift.im" } keepalive_interval = 90 -- (in seconds, default is 60 ) keepalive_timeout = 300 -- (in seconds, default is 593 ) ``` Compatibility ============= ------- ----------------------- 0.11 Works 0.10 Works 0.9 Works ------- -----------------------
