Skip to content

Issue 1618 review sbweeden attachment transport #3

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

Merged
merged 2 commits into from
Oct 1, 2021
Merged

Issue 1618 review sbweeden attachment transport #3

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d562282
Describe how to determine authenticator attachment from transports
emlun Sep 17, 2021
183d059
Accept @equalsJeffH's rewrite of #sctn-attachment-from-transports
emlun Oct 1, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2429,6 +2429,26 @@ To remove the need to parse CBOR at all in many cases, {{AuthenticatorAttestatio

Note: {{AuthenticatorAttestationResponse/getPublicKey()}} and {{AuthenticatorAttestationResponse/getAuthenticatorData()}} were only added in level two of this spec. [=[RPS]=] SHOULD use feature detection before using these functions by testing the value of `'getPublicKey' in AuthenticatorAttestationResponse.prototype`. [=[RPS]=] that require this function to exist may not interoperate with older user-agents.


#### Determining Authenticator Attachment from Credential Transports #### {#sctn-attachments-from-transports}

As a part of creating a {{PublicKeyCredential}} object, as the result of a [=registration ceremony|registration=] or [=authentication ceremony=], the [=client platform=] determines the [=authenticator attachment modality=] and reports it in {{PublicKeyCredential/authenticatorAttachment}}. This section defines how to make that determination.

If the client platform
<dl class="switch">
: cannot determine the {{transports}} used or the transport is not a member of {{AuthenticatorTransport}}, then
:: the [=authenticator attachment modality=] is unknown, and the value of {{PublicKeyCredential/authenticatorAttachment}} MUST be set to null.

: used an {{AuthenticatorTransport/internal}} transport, then
:: {{PublicKeyCredential/authenticatorAttachment}} MUST be set to "platform".

: used a {{transports|transport}} that is a member of {{transports}} other than {{AuthenticatorTransport/internal}},
:: {{PublicKeyCredential/authenticatorAttachment}} MUST be set to "cross-platform".

Note: An [=authenticator's=] [=authenticator attachment modality|attachment modality=] could change over time.
For example, a mobile phone might at one time only support [=platform attachment=]
but later receive updates to support [=cross-platform attachment=] as well.

### Web Authentication Assertion (interface <dfn interface>AuthenticatorAssertionResponse</dfn>) ### {#iface-authenticatorassertionresponse}

The {{AuthenticatorAssertionResponse}} interface represents an [=authenticator=]'s response to a client's request for
Expand Down