File

mod_http_oauth2/html/device.html @ 6281:9d88c3d9eea5

mod_http_oauth2: Enforce the registered grant types Thus a client can limit itself to certain grant types. Not sure if this prevents any attacks, but what was the point of including this in the registration if it was not going to be enforced? This became easier to do with client_id being available earlier.
author Kim Alvefur <zash@zash.se>
date Mon, 02 Jun 2025 20:55:20 +0200
parent 5653:401356232e1b
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>