Mercurial > prosody-modules
view mod_email_pass/templates/token.html @ 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 | 7dbde05b48a9 |
children |
line wrap: on
line source
<!DOCTYPE html> <html> <head> <link rel="stylesheet" type="text/css" href="style.css" /> <meta charset="utf-8"> <title>Reseto de la clave de tu cuenta Jabber</title> </head> <body> <div id="estilo" class="formulario"> <h1>Reseteo de la clave de tu cuenta Jabber</h1> <form action="{path}?{token}" method="POST"> <p class="error">{notice}</p> <label> Token: </label> <input name="token" value="{token}" required readonly> <div class="spacer"></div> <label> Contraseña: </label> <input name="newpassword" type="password" required size="35"> <div class="spacer"></div> <input id="button" class="button" type="submit" value="Cambiar!"> <div class="spacer"></div> </form> </div> </body> </html>