DRAFT: Backup eligibility parameter during registration #1744
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.
Brainstorm idea for #1739. This is meant to facilitate discussion, not a fully-formed proposal.
Something like this would enable the client to optimize the user interaction to increase the chance that the registration completes successfully. I note in #1714 (comment) that since we now have the
BS
andBE
flags in the authenticator data, that to me signals that this is a significant credential property that there should perhaps be a feature toggle for.However the argument against (again, see #1714 (comment)) is that we don't want RPs to see this as a "make it more secure" parameter and just set it to
"forbidden"
without further consideration. So in order to respect the interests of the user, this proposal allows the client to let the user override the RP's preference if desired.Perhaps something like this could be a reasonable middle-ground? Is the risk of ecosystem fragmentation still too great? Is it not powerful enough to be useful to RPs? Discuss!
Preview | Diff