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.

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

Adding references to FIDO AR Papers #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
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
7 changes: 6 additions & 1 deletion HowToFIDO.md
Original file line number Diff line number Diff line change
Expand Up @@ -755,7 +755,7 @@ A concern around the use of FIDO authenticators is device loss: what
happens when a user loses their FIDO authenticator? How will they be
able to get back into (i.e., “recover”) their account? **Our general
recommendation is to encourage the user to register a *second*
authenticator as backup**, but there are a few caveats to consider:
authenticator as backup** [16] [17], but there are a few caveats to consider:

- If a user's *only* registered authenticator is a *platform*
authenticator that is used ***only*** for
Expand Down Expand Up @@ -977,3 +977,8 @@ a UVRA</span>](#signing-in-with-a-uvra).
15. Historically, we used the term "resident key" to refer to what will
be known as "discoverable credentials" in the upcoming WebAuthn L2
and CTAP2.1 specs.

16. Recommended Account Recovery Practices for FIDO Relying Parties, https://fidoalliance.org/recommended-account-recovery-practices/

17. White Paper: Multiple Authenticators for Reducing Account-Recovery Needs for FIDO-Enabled Consumer Accounts, https://fidoalliance.org/white-paper-multiple-authenticators-for-reducing-account-recovery-needs-for-fido-enabled-consumer-accounts/