-
Notifications
You must be signed in to change notification settings - Fork 10
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
Skip empty user IDs in getAssertion #32
Comments
robin-nitrokey
added a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Jul 7, 2023
Users with an empty ID should not be returned by getAssertion to avoid compatibility issues. trussed-dev#32
robin-nitrokey
added a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Jul 10, 2023
Users with an empty ID should not be returned by getAssertion to avoid compatibility issues. Fixes: trussed-dev#32
nickray
pushed a commit
to robin-nitrokey/fido-authenticator
that referenced
this issue
Sep 13, 2023
Users with an empty ID should not be returned by getAssertion to avoid compatibility issues. Fixes: trussed-dev#32
nickray
pushed a commit
that referenced
this issue
Sep 13, 2023
Users with an empty ID should not be returned by getAssertion to avoid compatibility issues. Fixes: #32
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Users with an empty ID should not be returned by getAssertion to avoid compatibility issues. This is checked by the CTAP2 test suite.
The text was updated successfully, but these errors were encountered: