Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Created linkable definition for WebAuthn Extensions and linked to it … #1193

Merged
merged 2 commits into from Apr 17, 2019
Merged

Created linkable definition for WebAuthn Extensions and linked to it … #1193

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a946a09
Created linkable definition for WebAuthn Extensions and linked to it …
futureimperfect Mar 25, 2019
bd638f3
Addressed @emlun's comments about additional occurrences of WebAuthn …
futureimperfect Apr 6, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 9 additions & 9 deletions index.bs
View file
Open in desktop
Expand Up @@ -1908,7 +1908,7 @@ optionally evidence of [=user consent=] to a specific transaction.
example, the caller may request that only authenticators with certain capabilities be used to create the credential, or
that particular information be returned in the [=attestation object=]. Some extensions are defined in [[#extensions]];
consult the IANA "WebAuthn Extension Identifier" registry established by [[!WebAuthn-Registries]] for an up-to-date list
of registered WebAuthn Extensions.
of registered [=WebAuthn Extensions=].
</div>

### Public Key Entity Description (dictionary <dfn dictionary>PublicKeyCredentialEntity</dfn>) ### {#dictionary-pkcredentialentity}
Expand Down Expand Up @@ -2213,7 +2213,7 @@ SHOULD be aborted.
};
</xmp>

This is a dictionary containing the [=client extension input=] values for zero or more WebAuthn extensions, as defined in [[#extensions]].
This is a dictionary containing the [=client extension input=] values for zero or more [=WebAuthn Extensions=].


## Authentication Extensions Client Outputs (typedef {{AuthenticationExtensionsClientOutputs}}) ## {#iface-authentication-extensions-client-outputs}
Expand All @@ -2223,7 +2223,7 @@ This is a dictionary containing the [=client extension input=] values for zero o
};
</xmp>

This is a dictionary containing the [=client extension output=] values for zero or more WebAuthn extensions, as defined in [[#extensions]].
This is a dictionary containing the [=client extension output=] values for zero or more [=WebAuthn Extensions=].


## Authentication Extensions Authenticator Inputs (typedef {{AuthenticationExtensionsAuthenticatorInputs}}) ## {#iface-authentication-extensions-authenticator-inputs}
Expand All @@ -2232,7 +2232,7 @@ This is a dictionary containing the [=client extension output=] values for zero
typedef record<DOMString, DOMString> AuthenticationExtensionsAuthenticatorInputs;
</xmp>

This is a dictionary containing the [=authenticator extension input=] values for zero or more WebAuthn extensions, as defined in [[#extensions]].
This is a dictionary containing the [=authenticator extension input=] values for zero or more [=WebAuthn Extensions=].


## Supporting Data Structures ## {#supporting-data-structures}
Expand Down Expand Up @@ -3654,7 +3654,7 @@ different versions are thus treated as different formats, e.g., `packed2` as a n
format.

The following sections present a set of currently-defined and registered attestation statement formats and their identifiers.
The up-to-date list of registered WebAuthn Extensions is maintained in the IANA "WebAuthn Attestation Statement Format
The up-to-date list of registered [=WebAuthn Extensions=] is maintained in the IANA "WebAuthn Attestation Statement Format
Identifier" registry established by [[!WebAuthn-Registries]].


Expand Down Expand Up @@ -4187,7 +4187,7 @@ The none attestation statement format is used to replace any [=authenticator=]-p
: Verification procedure
:: Return implementation-specific values representing [=attestation type=] [=None=] and an empty [=attestation trust path=].

# WebAuthn Extensions # {#extensions}
# <dfn>WebAuthn Extensions</dfn> # {#extensions}

The mechanism for generating [=public key credentials=], as well as requesting and generating Authentication assertions, as
defined in [[#api]], can be extended to suit particular use cases. Each case is addressed by defining a <dfn>registration
Expand Down Expand Up @@ -4230,14 +4230,14 @@ that it supports, and returns the [=CBOR=] [=authenticator extension output=] fo
the [=client extension processing=] for [=authenticator extensions=] is to use the [=authenticator extension output=] as an
input to creating the [=client extension output=].

All WebAuthn extensions are OPTIONAL for both clients and authenticators. Thus, any extensions requested by a [=[RP]=] MAY be
All [=WebAuthn Extensions=] are OPTIONAL for both clients and authenticators. Thus, any extensions requested by a [=[RP]=] MAY be
ignored by the client browser or OS and not passed to the authenticator at all, or they MAY be ignored by the authenticator.
Ignoring an extension is never considered a failure in WebAuthn API processing, so when [=[RPS]=] include extensions with any
API calls, they MUST be prepared to handle cases where some or all of those extensions are ignored.

Clients wishing to support the widest possible range of extensions MAY choose to pass through any extensions that they do not
recognize to authenticators, generating the [=authenticator extension input=] by simply encoding the [=client extension input=]
in CBOR. All WebAuthn extensions MUST be defined in such a way that this implementation choice does not endanger the user's
in CBOR. All [=WebAuthn Extensions=] MUST be defined in such a way that this implementation choice does not endanger the user's
security or privacy. For instance, if an extension requires client processing, it could be defined in a manner that ensures such
a naïve pass-through will produce a semantically invalid [=authenticator extension input=] value, resulting in the extension
being ignored by the authenticator. Since all extensions are OPTIONAL, this will not cause a functional failure in the API
Expand Down Expand Up @@ -4270,7 +4270,7 @@ Supporting this capability can facilitate innovation, allowing authenticators to
and [=[RPS]=] to use them before there is explicit support for them in clients.

The IANA "WebAuthn Extension Identifier" registry established by [[!WebAuthn-Registries]] can be consulted
for an up-to-date list of registered WebAuthn Extensions.
for an up-to-date list of registered [=WebAuthn Extensions=].


## Extension Identifiers ## {#sctn-extension-id}
Expand Down