view mod_http_oauth2/html/device.html @ 5616:59d5fc50f602

mod_http_oauth2: Implement refresh token rotation Makes refresh tokens one-time-use, handing out a new refresh token with each access token. Thus if a refresh token is stolen and used by an attacker, the next time the legitimate client tries to use the previous refresh token, it will not work and the attack will be noticed. If the attacker does not use the refresh token, it becomes invalid after the legitimate client uses it. This behavior is recommended by draft-ietf-oauth-security-topics
author Kim Alvefur <zash@zash.se>
date Sun, 23 Jul 2023 02:56:08 +0200
parents 1893ae742f66
children 8de02381e80a
line wrap: on
line source

<!DOCTYPE html>
<html>
<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>
	<main>
	<h1>{site_name}</h1>
	<fieldset>
	<legend>Device Authorization</legend>
	{error&<div class="error">
		<p>{error.text}</p>
	</div>}
{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="user-code" required >
		<input type="submit" value="Continue">
	</form>}
	</fieldset>
	</main>
</body>
</html>