Mercurial > prosody-modules
view mod_invites_tracking/README.md @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +0100 |
parents | 32f1f18f4874 |
children |
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.