[Spec] Add note on SPC opt-in, and misc clarifications #183
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
This PR adds a note about what SPC opt-in means today (required for any use of SPC) versus in our preferred future (required for 3p use of SPC). It also contains a set of small clarifications, e.g. updating the 'steps to silently determine...' to acknowledge that an RP ID will likely be needed.
|
No major changes here (and nothing normative), just some minor clarifications I felt were useful as I look at how we might change the spec in the medium-term future. I'm hoping to also follow this up with a PR explicitly spec-ing the user-agent caching mechanism, but that may take a while :/ |
ianbjacobs
approved these changes
Apr 28, 2022
| [[webauthn-3#relying-party-identifier|Relying Party Identifier]] and a | ||
| [=credential ID=], silently (i.e., without user interaction) determine if | ||
| the credential represented by that credential ID is available for the | ||
| current device (i.e., could be successfully used as part of a WebAuthn |
There was a problem hiding this comment.
I am wondering about the phrase "current device" here and elsewhere in the API. It might be overly constraining in light of synched credentials and CABLE. Would it be more inclusive to say "current API call"?
There was a problem hiding this comment.
Great question. I'm not sure how best to resolve that yet (maybe worth adding a minor comment to #174), so going to leave for now.
github-actions bot
added a commit
that referenced
this pull request
Apr 29, 2022
SHA: 874d9d6 Reason: push, by @stephenmcgruer Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
This PR adds a note about what SPC opt-in means today (required for any use of
SPC) versus in our preferred future (required for 3p use of SPC). It also
contains a set of small clarifications, e.g. updating the 'steps to silently
determine...' to acknowledge that an RP ID will likely be needed.
Preview | Diff