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

Add None attestation case to RP ops registration step 16 #1145

Merged
merged 1 commit into from
Feb 13, 2019
Merged

Add None attestation case to RP ops registration step 16 #1145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3470,7 +3470,8 @@ When registering a new credential, represented by an {{AuthenticatorAttestationR
<code>[=aaguid=]</code> in the <code>[=attestedCredentialData=]</code> in |authData|.

1. Assess the attestation trustworthiness using the outputs of the [=verification procedure=] in step 14, as follows:
- If [=self attestation=] was used, check if [=self attestation=] is acceptable under [=[RP]=] policy.
- If [=None|no attestation=] was provided, verify that [=None=] attestation is acceptable under [=[RP]=] policy.
- If [=self attestation=] was used, verify that [=self attestation=] is acceptable under [=[RP]=] policy.
- If [=ECDAA=] was used, verify that the [=identifier of the ECDAA-Issuer public key=] used is included in the set of
acceptable trust anchors obtained in step 15.
- Otherwise, use the X.509 certificates returned by the [=verification procedure=] to verify that the attestation public key
Expand Down