Bug 274217 – navigator.credentials.create return Type error when authenticatorAttachment is null

• Status: NEW
• Component: WebKit Misc.

[chunli]

We found that we couldn't add a passkey in Safari due to a weird "Type error" from navigator.credentials.create, while other browsers like Chrome, Firefox, and Edge continued to work without any issues. The root cause was that our backend didn't return the authenticatorAttachment to the frontend, and the frontend passed authenticatorAttachment = null to navigator.credentials.create. We fixed the issue by removing it when the value was null, but according to the WebAuthn spec(https://www.w3.org/TR/webauthn-2/#dom-authenticatorselectioncriteria-authenticatorattachment), Safari should ignore the unknown value.

From the spec:
authenticatorAttachment, of type DOMString
If this member is present, eligible authenticators are filtered to only authenticators attached with the specified § 5.4.5 Authenticator Attachment Enumeration (enum AuthenticatorAttachment). The value SHOULD be a member of AuthenticatorAttachment but client platforms MUST ignore unknown values, treating an unknown value as if the member does not exist.

[Radar WebKit Bug Importer]

<rdar://problem/128177000>

[Karl Dubost]

@chunli
thanks for the report. A testcase would be helpful or at least the code when this manifests.

[Karl Dubost]

Probably also need to double check with
https://wpt.fyi/results/webauthn?label=master&label=experimental&aligned&q=webauthn%20safari%3Afail

[chunli]

Hi, @karlcow

Thank you for provide the wpt.fyi link. I think the test `authenticatorSelection attachment null` in https://wpt.fyi/results/webauthn/createcredential-passing.https.html?label=master&label=experimental&aligned&q=webauthn%20safari%3Afail matched what I reported, and I saw the Safari still red with `TypeError: Type error` error.

I think the test code is: 
https://github.com/web-platform-tests/wpt/blob/42fc3843b3/webauthn/createcredential-passing.https.html#L112