2009809 - [wpt-sync] Sync PR 57128 - Add getCoseKeyType - missing function in secure payment confirmation.

Status: NEW

(Core :: DOM: Web Payments, task, P4)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Sync web-platform-tests PR 57128 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/57128
Details from upstream follow.

Slobodan Pejic <[e-mail]> wrote:

Add getCoseKeyType - missing function in secure payment confirmation.

Bug: 474614620
Change-Id: I7d1cb5bbefbeb63958434f3ff8147b7c67743aa4

Reviewed-on: https://chromium-review.googlesource.com/7418545
WPT-Export-Revision: 768fb9cf55eb8ef3c7f123835b3489a6459442aa

Comment 1

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=8809398d311a694a979f3c6c57a296fbe6ab1642

Comment 2

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 5 tests and 3 subtests

Status Summary

Firefox

OK : 4
PASS : 3
FAIL : 8
ERROR : 1

Chrome

OK : 4
PASS : 9
FAIL : 2
ERROR : 1

Safari

OK : 3
PASS : 3
FAIL : 7
TIMEOUT: 2
ERROR : 1

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

• /secure-payment-confirmation/authentication-accepted-bbk-created.https.html [wpt.fyi]
  • Creates a browser bound key on authentication.: FAIL (Chrome: FAIL, Safari: FAIL)
  • If ES256 is supported creates a browser bound key on authentication.: FAIL (Chrome: PASS, Safari: FAIL)
  • If RS256 is supported creates a browser bound key on authentication.: FAIL (Chrome: PASS, Safari: FAIL)
• /secure-payment-confirmation/authentication-accepted-bbk-per-passkey.https.html [wpt.fyi]
  • If a browser bound keys are created on authentication then a different browser bound key is created for a different passkey: FAIL (Chrome: PASS, Safari: FAIL)
• /secure-payment-confirmation/authentication-accepted-bbk-reused.https.html [wpt.fyi]
  • Uses the same browser bound key authentication as enrollment.: FAIL (Chrome: FAIL, Safari: FAIL)
  • If ES256 is supported, the browser bound key is the same during authentication as enrollment.: FAIL (Chrome: PASS, Safari: FAIL)
  • If RS256 is supported, the browser bound key is the same during authentication as enrollment.: FAIL (Chrome: PASS, Safari: FAIL)
• /secure-payment-confirmation/enrollment-bbk-per-passkey.https.html [wpt.fyi]
  • If a browser bound keys are created on enrollment then a different browser bound key is created for a different passkey: FAIL (Chrome: PASS, Safari: TIMEOUT)
• /secure-payment-confirmation/enrollment-bbk.https.html [wpt.fyi]: ERROR (Chrome: ERROR, Safari: ERROR)