Bug 281092 – Updates to getClientCapabilities to match latest WebAuthn spec

• Status: RESOLVED
• Resolution: MOVED
• Component: WebKit Misc.

[Tim Cappalli]

Couple of updates are needed for getClientCapabilities() to match the current L3 spec[1]

A. WebKit supports Related Origin Requests but is not reporting that support (using `relatedOrigins` [2]) in getClientCapabilities(). This is critical for the usability of the related origins feature by RPs.
B. The capability for Conditional Mediation (aka autofill UI) was renamed [3] to `conditionalGet`[4] when `conditionalCreate` was added for consistency.

[1] https://w3c.github.io/webauthn/#sctn-getClientCapabilities
[2] https://w3c.github.io/webauthn/#dom-clientcapability-relatedorigins
[3] https://github.com/w3c/webauthn/pull/2061
[4] https://w3c.github.io/webauthn/#dom-clientcapability-conditionalget


Here is the output of getClientCapabilities() in Safari Technical Preview 205:

{"passkeyPlatformAuthenticator":true,"hybridTransport":true,"conditionalMediation":true,"conditionalCreate":true,"userVerifyingPlatformAuthenticator":true}

[Radar WebKit Bug Importer]

<rdar://problem/137539823>

[Brent Fulgham]

The cause of this bug was outside of the WebKit Open Source project. The fix will be shipped to customers in a future update. We will update this bug when we have a public seed that can be tested.