Mercurial > prosody-modules
view mod_invites_tracking/README.md @ 5390:f2363e6d9a64
mod_http_oauth2: Advertise the currently supported id_token signing algorithm
This field is REQUIRED. The algorithm RS256 MUST be included, but isn't
because we don't implement it, as that would require implementing a pile
of additional cryptography and JWT stuff. Instead the id_token is
signed using the client secret, which allows verification by the client,
since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under
Symmetric Signatures.
OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that
are not supported here, but that's okay because this is served from the
RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 30 Apr 2023 16:13:40 +0200 |
| 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.