prosody-modules
527c747711f3
mod_graceful_shutdown/README.markdown
Software / code / prosody-modules
File
mod_graceful_shutdown/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 | 4898:999e7cb7f6d9 |
line wrap: on
line source
::: {.alert .alert-warning} This module is an experiment about a more graceful shutdown process. Graceful shutdown has now been implemented in Prosody trunk and will be part 0.12. See [issue #1225](https://issues.prosody.im/1225) for details. ::: Why === When shutting down, a number of sessions, connections and other things are teared down. Due to all these things happening very quickly, sometimes e.g. client unavailable notifications don't make it to all remote contacts because the server-to-server connections are teared down just after. How === This module works by breaking the shutdown process into separate steps with a brief pause between them. It goes something like this 1. Stop accepting new client connections. 2. Close all client connections. 3. Fire event for everything else. 4. Tell `net.server` to quit the main loop. 5. ??? 6. Still here? Kill itself.
