Mercurial > prosody-modules
view mod_http_host_status_check/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 | 2a16a6c67288 |
| children | 694b62d8a82f |
line wrap: on
line source
--- labels: Stage-Beta summary: HTTP Host Status Check ... Introduction ============ This module exposes serves over HTTP the information collected by [mod\_host\_status\_check] and [mod\_host\_status\_heartbeat] in a convenient format for automated monitoring tools. Configuration ============= [mod\_http\_status\_check] relies on Prosodys HTTP server and mod\_http for serving HTTP requests. See [Prosodys HTTP server documentation][doc:http] for information about how to configure ports, HTTP Host names etc. Simply add this module to modules\_enabled for the host you would like to serve it from. There is a single configuration option: ``` {.lua} -- The maximum number of seconds that a host can go without sending a heartbeat, -- before we mark it as TIMEOUT (default: 5) status_check_heartbeat_threshold = 5; ``` Compatibility ============= Works with Prosody 0.9.x and later.