Mercurial > prosody-modules
view mod_reload_modules/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-Stable' summary: Automatically reload modules with the config ... Introduction ------------ By default Prosody does not reload modules at runtime unless instructed to via one of its admin interfaces. However sometimes you want to easily reload a module to apply new settings when the config changes. mod\_reload\_modules will reload a set list of modules every time Prosody reloads its config (e.g. on SIGHUP). Configuration ------------- Add "reload\_modules" to modules\_enabled. Then the list of modules to reload using the 'reload\_modules' option in your config like so: reload_modules = { "groups", "tls" } This would reload mod\_groups and mod\_tls whenever the config is reloaded. Note that on many systems this will be at least daily, due to logrotate. Compatibility ------------- ----- ------- 0.9 Works ----- -------