Mercurial > prosody-modules
view mod_list_inactive/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 | 0c01444f8bc2 |
| children |
line wrap: on
line source
Description =========== This module lists those users, who haven't used their account in a defined time-frame. Dependencies ============ [mod_lastlog] must be enabled to collect the data used by this module. Usage ===== prosodyctl mod_list_inactive example.com time [format] Time is a number followed by 'day', 'week', 'month' or 'year' Formats are: --------- ------------------------------------------------ delete `user:delete"user@example.com" -- last action` default `user@example.com` event `user@example.com last action` --------- ------------------------------------------------ Example ======= prosodyctl mod_list_inactive example.com 1year Help ==== prosodyctl mod_list_inactive