Skip to content

Commit

Permalink
Recommend RPs to store transport hints
Browse files Browse the repository at this point in the history
  • Loading branch information
emlun committed Sep 11, 2019
1 parent 24ecf51 commit 5781243
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions index.bs
Expand Up @@ -4081,6 +4081,11 @@ In order to perform a [=registration ceremony=], the [=[RP]=] MUST proceed as fo
in <code>|authData|.[=attestedCredentialData=]</code>, as appropriate for the [=[RP]=]'s system.
- Associate the <code>[=credentialId=]</code> with a new stored [=signature counter=] value
initialized to the value of <code>|authData|.[=signCount=]</code>.
- OPTIONALLY, associate the <code>[=credentialId=]</code> with the transport hints
returned by calling <code>|credential|.{{AuthenticatorAttestationResponse/getTransports()}}</code>.
It is RECOMMENDED to use these to populate the {{PublicKeyCredentialDescriptor/transports}}
of the {{PublicKeyCredentialRequestOptions/allowCredentials}} option in future {{CredentialsContainer/get()}} calls
to help the [=client=] know how to find a suitable [=authenticator=].

1. If the attestation statement |attStmt| successfully verified but is not trustworthy per step 21 above, the [=[RP]=] SHOULD fail
the [=registration ceremony=].
Expand Down

0 comments on commit 5781243

Please sign in to comment.