[webauthn] Extension input processing directions are inconsistent (#2439)

emlun has just created a new issue for https://github.com/w3c/webauthn:

== Extension input processing directions are inconsistent ==
[ยง9.3. Extending Request Parameters](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#sctn-extension-request-parameters) reads:

>[...] Clients SHOULD ignore extensions with an invalid [client extension input](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#client-extension-input). [...]

However, several extensions including [`appid`](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#sctn-appid-extension), [`appidExclude`](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#sctn-appid-exclude-extension), [`prf`](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#prf-extension) and [`largeBlob`](https://www.w3.org/TR/2026/CR-webauthn-3-20260113/#sctn-large-blob-extension) instruct the client to throw errors in some error cases. This paints an inconsistent picture of how clients should behave: should invalid extension inputs be ignored, or return hard errors?

Arguments in favour of ignoring invalid inputs:
- Increases the likelihood that the ceremony completes successfully even if some extension inputs are incorrect.

Arguments in favour of returning an error:
- Makes it easier for RP developers to detect mistakes early and correct them before they impact users.
- Reduces the risk of creating a credential without required properties. For example, an RP that sets `enforceCredentialProtectionPolicy: true` but fails to set `credentialProtectionPolicy` correctly would likely prefer an early error over proceeding to create a credential with a credential protection policy lower than requested.


## Proposed Change

Change the directive "Clients SHOULD ignore extensions with an invalid client extension input" to something like "Clients SHOULD ignore client extension inputs for unknown extensions, and SHOULD return an error for invalid or malformed client extension inputs for known extensions".

Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2439 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 1 July 2026 11:47:00 UTC