Register publickey-credentials-remote-client-data-json feature - #586
Open
bobomb wants to merge 1 commit into
Open
Register publickey-credentials-remote-client-data-json feature#586bobomb wants to merge 1 commit into
bobomb wants to merge 1 commit into
Conversation
bobomb
force-pushed
the
webauthn-remote-client-data-json-feature
branch
from
June 24, 2026 14:01
c0ba02d to
7ea2ff6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
publickey-credentials-remote-client-data-jsonpolicy-controlled feature to the registry (features.md).What this gates
The feature controls the remoteClientDataJSON WebAuthn client extension, which lets an authorized remote-desktop web client forward a verbatim
clientDataJSONto the local authenticator (rather than having the local user agent reconstruct it).Where it is normatively defined
The feature is defined by the Web Authentication API in its Permissions Policy integration section, consistent with the registry convention that "the exact definition of the behaviour controlled by each feature belongs in the spec which defines the feature." The registry row therefore points at the same WebAuthn section as
publickey-credentials-get.Default allowlist
Unlike
publickey-credentials-createandpublickey-credentials-get(default allowlistself), this feature has a default allowlist ofnone. It is disabled for all origins, including the top-level document, unless explicitly delegated. The WebAuthn spec also designates it a powerful feature with default permission state"denied".Note that default allowlist of
noneis currently not normative, but exists as a proposed change in #515Placement
Added to the Standardized Features table (the normative definition is already integrated into the WebAuthn editor's draft). Browser support is marked
ChromeOpenpending the implementation landing as experimental.