Add Hybrid transport support #670
Merged
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
|
Thanks! This should fix my second point in #2559 |
|
To resolve failed tests, another pull-request is created: #672 |
ynojima
force-pushed
the
add-hybrid-transport
branch
from
eaeeea3 to
b042ba4
Compare
|
Rebased to pull #672 changes |
|
@vietj or @tsegismont can we get this moving please? |
|
can you backport this @ynojima ? |
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.
Add support for "hybrid" authenticator transport (W3C Spec: w3c/webauthn#1755)
"hybrid" transport is needed to use smartphones as a security key for client platforms like PC.
Addresses #665