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

Pass FIDO2 conformance GetAssertion Resp-3 P-4/P-7 tests #199

Closed
grzuy opened this issue May 8, 2019 · 7 comments · Fixed by #273
Closed

Pass FIDO2 conformance GetAssertion Resp-3 P-4/P-7 tests #199

grzuy opened this issue May 8, 2019 · 7 comments · Fixed by #273

Comments

@grzuy
Copy link
Contributor

grzuy commented May 8, 2019

P-4 Send a valid ServerAuthenticatorAssertionResponse both authenticatorData.flags.UV and authenticatorData.flags.UP are not set, for userVerification set to "preferred", and check the server succeeds

P-7 Send a valid ServerAuthenticatorAssertionResponse both authenticatorData.flags.UV and authenticatorData.flags.UP are not set, for userVerification set to "discouraged", and check the server succeeds

> F-5 Send a valid ServerAuthenticatorAssertionResponse with only authenticatorData.flags.UP is set, for userVerification set to "required", and check that the server returns an error (Moved to #205)

@grzuy
Copy link
Contributor Author

grzuy commented May 8, 2019

This would benefit from #194, because of receiving the original options in the verification process.

@grzuy grzuy pinned this issue May 19, 2019
@grzuy
Copy link
Contributor Author

grzuy commented May 19, 2019

Splitting F-5 into it's own issue => #205

@grzuy grzuy changed the title Pass FIDO2 conformance GetAssertion Resp-3 user verification tests Pass FIDO2 conformance GetAssertion Resp-3 P-4/P-7 tests May 19, 2019
@grzuy grzuy unpinned this issue May 19, 2019
@grzuy
Copy link
Contributor Author

grzuy commented May 19, 2019

These P-4 and P-7 failures are strange to me...

FIDO2 conformance tools expect server to succeed when UP is not set, while WebAuthn spec says UP must always be set in step 12.

@grzuy
Copy link
Contributor Author

grzuy commented May 19, 2019

Already reported in fido-alliance/conformance-test-tools-resources#434.

@grzuy
Copy link
Contributor Author

grzuy commented Jul 13, 2019

Still not sure how to proceed with this.

I am currently trying to better understand what's the stance of the FIDO2 conformance tools about this matter. See fido-alliance/conformance-test-tools-resources#434.

@bdewater
Copy link
Collaborator

bdewater commented Aug 21, 2019

WebAuthn is using a subset of FIDO2 in an online browser, silent authentication is undesirable from a privacy perspective in this context. But for some scenarios (e.g. employees logged in to a POS system, a clerk at a bank, etc) you might want to silently re-authenticate every minute and automatically logout the user if that fails. I guess you could even preregister keys and send them to your customers and use it as a form of software copy protection that way.

So the question is, do we want to support just WebAuthn or FIDO2? I'd lean towards the first for default settings but expose the knobs for people who know what they are doing.

@grzuy
Copy link
Contributor Author

grzuy commented Aug 21, 2019

So the question is, do we want to support just WebAuthn or FIDO2? I'd lean towards the first for default settings but expose the knobs for people who know what they are doing.

Agree.

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.

2 participants