-
Notifications
You must be signed in to change notification settings - Fork 27
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
NonUniqueDeviceError while Yubikey NEO is connected #482
Comments
The first issue: accessing the Nitrokey 3 while another FIDO2/U2F device is present should be solvable by also passing the specific device like that:
With the device being what is written in the first column in The other issue, the U2F register is pretty weird, also just tested this successfully on webauthn.io using 2x Nitrokey 3. Registering the device works with both devices and both will ask for the user confirmation (user presence) and the one which is confirmed will then be registered for the service. On a first glance this looks like the Yubikey Neo does not behave as expected (defined by the spec). Although it has no FIDO2 capabilities it comes with U2F (which likely is also the reason the non-unique error is shown by |
Thanks for your answer. Do you have any idea how to select the device on Windows?
Tried various parts from that output but it always throws errors like |
Hi,
I use a YubiKey NEO along with my NK3 (for static password and some sites which only support Yubico OTP).
As long as the Yubikey is connected to my PC, I am unable to interact with my NK3:
I am also unable to register the NK3 for U2F on any website.
When I remove the Yubikey, everythink works fine. Happens on
v1.5.0
, just upgraded tov1.6.0-rc.1
, same issue.Is this expected behaviour? The Yubikey NEO doesn't even support FIDO2.
Windows 11 23H2 (Build 22631.2715)
The text was updated successfully, but these errors were encountered: