Mercurial > prosody-modules
view mod_lastlog2/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 | fd582067c732 |
children | c5df6d53f17f |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Record last timestamp of events --- # Introduction Similar to [mod_lastlog], this module records the last timestamp of various events, but keeps the last timestamp per type of event, instead of the last event. # Usage As with all modules, copy it to your plugins directory and then add it to the modules\_enabled list: ``` {.lua} modules_enabled = { -- other modules "lastlog2", } ``` # Configuration There are some options you can add to your config file: Name Type Default Description ---------------------- --------- --------- --------------------------------- lastlog\_ip\_address boolean false Log the IP address of the user? # Usage You can check a user's last activity by running: prosodyctl mod_lastlog username@example.com # Compatibility Version State --------- ------- Any *TBD*