Mercurial > prosody-modules
view mod_http_oauth2/html/device.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 | 401356232e1b |
| children |
line wrap: on
line source
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <title>{site_name} - Authorize{client&d} Device</title> <link rel="stylesheet" href="style.css" /> </head> <body> {error& <dialog open="" class="error"> <p>{error.text}</p> <form method="dialog"><button>dismiss</button></form> </dialog>} <header> <h1>{site_name}</h1> </header> <main> <fieldset> <legend>Device Authorization</legend> {client& <p>Authorization completed. You can go back to <em>{client.client_name}</em>.</p>} {client~ <p>Enter the code to continue.</p> <form method="get"> <input type="text" name="user_code" placeholder="XXXX-XXXX" aria-label="Code" required="" /> <button type="submit">Continue</button> </form>} </fieldset> </main> </body> </html>