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

ensure non-native Signature Assertions are passed-through #465

Closed
equalsJeffH opened this issue May 17, 2017 · 5 comments
Closed

ensure non-native Signature Assertions are passed-through #465

equalsJeffH opened this issue May 17, 2017 · 5 comments

Comments

@equalsJeffH
Copy link
Contributor

add support for UAF signature and assertion formats -- this will facilitate the millions of already-deployed UAF-capable smartphones to be usable with a WebAuthn-capable browser via CTAP (yes, a separate step is enabling the already-deployed UAF-capable smartphones to speak CTAP, which is possible)

this issue is addressed by these open PRs: #407 #408

@rlin1
Copy link
Contributor

rlin1 commented Oct 22, 2018

Proposal: Rephrase title to "ensure non-native signature assertions are being passed through"

@rlin1 rlin1 changed the title add support for UAF signature and assertion formats ensure non-native Signature Assertions are passed-through Oct 22, 2018
@rlin1
Copy link
Contributor

rlin1 commented Oct 22, 2018

Extend scope: Also allow potentially new signature assertion schemes as potentially required for Blockchain etc.

@rlin1
Copy link
Contributor

rlin1 commented Oct 22, 2018

see branch pass-through-other-assertion-formats

@nadalin nadalin modified the milestones: L2-WD-01, L2-WD-02 Feb 20, 2019
@nadalin
Copy link
Contributor

nadalin commented May 29, 2019

@rlin1 Please create a PR

@rlin1
Copy link
Contributor

rlin1 commented May 29, 2019

two changes:
a) ensure existing language in the spec does not preclude other assertions to go through
b) reference a specific assertion format that should be passed through (UAF).

@equalsJeffH equalsJeffH removed their assignment Jun 11, 2019
@rlin1 rlin1 modified the milestones: L2-WD-02, L3-WD-01 Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@equalsJeffH @rlin1 @nadalin and others