Daniel Rubery
150b5ab596
Automatic update from web-platform-tests Add WPT for challenge alongside DBSC session instructions Registration endpoints should be able to set the challenge for the first refresh by providing a challenge alongside the session instructions. This WPT validates that. Fixed: 438783634 Change-Id: I955b42e7fbb8a7a31aee0ca67d4cc9f40962df5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6995386 Commit-Queue: Daniel Rubery <drubery@chromium.org> Reviewed-by: thefrog <thefrog@chromium.org> Cr-Commit-Position: refs/heads/main@{#1523647} -- wpt-commits: 5da57e8b7ae6d847e344450c67b25f368e800212 wpt-pr: 55180
74 lines
3.2 KiB
HTML
74 lines
3.2 KiB
HTML
<!DOCTYPE html>
|
|
<meta charset="utf-8">
|
|
<script src="/resources/testharness.js"></script>
|
|
<script src="/resources/testharnessreport.js"></script>
|
|
<script src="helper.js" type="module"></script>
|
|
|
|
<script type="module">
|
|
import { expireCookie, waitForCookie, addCookieAndSessionCleanup, configureServer, setupShardedServerState, documentHasCookie } from "./helper.js";
|
|
|
|
promise_test(async t => {
|
|
await setupShardedServerState();
|
|
const expectedCookieAndValue = "auth_cookie=abcdef0123";
|
|
const expectedCookieAndAttributes = `${expectedCookieAndValue};Domain=${location.hostname};Path=/device-bound-session-credentials`;
|
|
addCookieAndSessionCleanup(t);
|
|
|
|
// Configure server to send back a challenge before the session instructions.
|
|
await configureServer({
|
|
registrationSendsChallengeBeforeInstructions: true,
|
|
// Since registration fails, we use a cookie to tell us that the
|
|
// response was received.
|
|
registrationExtraCookies: [
|
|
{
|
|
nameAndValue: "dbsc_registration=done",
|
|
}
|
|
]
|
|
});
|
|
|
|
// Prompt starting a session, and wait until registration completes.
|
|
const loginResponse = await fetch('login.py');
|
|
assert_equals(loginResponse.status, 200);
|
|
await waitForCookie("dbsc_registration=done", /*expectCookie=*/true);
|
|
|
|
// Confirm that expiring the cookie does not refresh because registration failed.
|
|
expireCookie(expectedCookieAndAttributes);
|
|
assert_false(documentHasCookie(expectedCookieAndValue));
|
|
const authResponseAfterExpiry = await fetch('verify_authenticated.py');
|
|
assert_equals(authResponseAfterExpiry.status, 403);
|
|
assert_false(documentHasCookie(expectedCookieAndValue));
|
|
}, "Registration can't send back 403 with challenge");
|
|
|
|
promise_test(async t => {
|
|
await setupShardedServerState();
|
|
const expectedCookieAndValue = "auth_cookie=abcdef0123";
|
|
const expectedCookieAndAttributes = `${expectedCookieAndValue};Domain=${location.hostname};Path=/device-bound-session-credentials`;
|
|
addCookieAndSessionCleanup(t);
|
|
|
|
// Configure server to send back a challenge alongside the session instructions.
|
|
await configureServer({
|
|
registrationSendsChallengeWithInstructions: true,
|
|
// Since registration fails, we use a cookie to tell us that the
|
|
// response was received.
|
|
registrationExtraCookies: [
|
|
{
|
|
nameAndValue: "dbsc_registration=done",
|
|
}
|
|
]
|
|
});
|
|
|
|
// Prompt starting a session, and wait until registration completes.
|
|
const loginResponse = await fetch('login.py');
|
|
assert_equals(loginResponse.status, 200);
|
|
await waitForCookie("dbsc_registration=done", /*expectCookie=*/true);
|
|
|
|
// Confirm that expiring the cookie does a refresh because registration succeeded.
|
|
expireCookie(expectedCookieAndAttributes);
|
|
assert_false(documentHasCookie(expectedCookieAndValue));
|
|
const authResponseAfterExpiry = await fetch('verify_authenticated.py');
|
|
// The server verifies during refresh that the challenge value is the custom
|
|
// one set at registration time.
|
|
assert_equals(authResponseAfterExpiry.status, 200);
|
|
assert_true(documentHasCookie(expectedCookieAndValue));
|
|
}, "Registration can send back challenge with session instructions");
|
|
</script>
|