prosody-modules
527c747711f3
mod_invites_tracking/README.md
Software / code / prosody-modules
File
mod_invites_tracking/README.md @ 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 | 4394:32f1f18f4874 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Store who created the invite to create a user account' ... Introduction ============ Invites are an intermediate way between opening registrations completely and closing registrations completely. By letting users invite other users to the server, an administrator exposes themselves again to the risk of abuse. To combat that abuse more effectively, this module allows to store (outside of the user’s information) who created an invite which was used to create the user’s account. Details ======= Add to `modules_enabled`. Caveats ======= - The information is not deleted even when the associated user accounts are deleted. - Currently, there is no way to make any use of that information.
