view mod_http_oauth2/html/error.html @ 5285:8e1f1eb00b58

mod_sasl2_fast: Fix harmless off-by-one error (invalidates existing tokens!) Problem: This was causing the key to become "<token>--cur" instead of the expected "<token>-cur". As the same key was used by the code to both set and get, it still worked. Rationale for change: Although it worked, it's unintended, inconsistent and messy. It increases the chances of future bugs due to the unexpected format. Side-effects of change: Existing '--cur' entries will not be checked after this change, and therefore existing FAST clients will fail to authenticate until they attempt password auth and obtain a new FAST token. Existing '--cur' entries in storage will not be cleaned up by this commit, but this is considered a minor issue, and okay for the relatively few FAST deployments.
author Matthew Wild <mwild1@gmail.com>
date Wed, 29 Mar 2023 16:12:15 +0100
parents aaa64c647e12
children 8d3e7b201ba4
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} - Error</title>
<link rel="stylesheet" href="style.css">
</head>
<body>
	<main>
	<h1>{site_name}<h1>
	<h2>Authentication error</h2>
	<p>There was a problem with the authentication request. If you were trying to sign in to a
	   third-party application, you may want to report this issue to the developers.</p>
	<div class="error">
		<p>{error.text}</p>
	</div>
	</main>
</body>
</html>