Adding Section 1.1. #21
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A new section 1.1 describes the unique of platform authenticator, user lock-out. Addressing this issue in the beginning part of the document makes it easier to describe different scenarios of platform and roaming authenticators, e.g., why some model is called "convenient", or "phising resistant".
eldanb
reviewed
Oct 11, 2021
| 16. This limitation may be solved if CTAP is implemented on the platform | ||
| authenticators. CTAP will enable platform authenticators to securely connect | ||
| to other devices via local transports like BLE and enable bootstrapping the | ||
| device. No off-the-shelf solution is available at the time of writing. |
There was a problem hiding this comment.
Do we want to include this in "how-to-fido"? Sounds like more of a TWG discussion than guidance for FIDO RPs?
| Platform authenticators have a unique issue which needs to be carefully considered when designing the flows and operations. | ||
|
|
||
| **Issue:** Platform authenticators cannot be connected to and used with other devices. Namely, they cannot bootstrap other devices [16]. | ||
|
|
There was a problem hiding this comment.
Perhaps start with a short recap of the difference between platform and roaming authenticators? Or if we just want to focus on the issue of lockout perhaps we can change the "Overview" section to "FIDO2 Usecases", and then add a 1.1 "Special considerations for Platform Authenticators"? In the future perhaps we can add 1.2 "Special considerations for Roaming Authenticators"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#3
New section 1.1 describes the unique issue of platform authenticators, user lock-out.
Addressing this issue in the beginning part of the document makes it easier to describe different scenarios of platform and roaming authenticators, e.g., why some models are called "convenient", or "phishing resistant", despite the fact that all the models use FIDO.
This section explains that the strongest reason why passwords are kept alive along with FIDO for the "convenient" model is to avoid user-lock out that will cause frictions of account recovery.