Mercurial > prosody-modules

view mod_http_oauth2/html/oob.html @ 5682:527c747711f3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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} - Authorization Code</title>
<link rel="stylesheet" href="style.css" />
</head>
<body>
	<header>
	<h1>{site_name}</h1>
	</header>
	<main>
	<h2>Your Authorization Code</h2>
	<p>Here’s your authorization code, copy and paste it into {client.client_name}</p>
	<div class="oob">
		<p><input readonly="" name="authorization_code" value="{authorization_code}" aria-label="Authorization Code"></p>
	</div>
	</main>
</body>
</html>