Firmware is latest. PIN is set and known to work. Yubikey NEO (FIDO U2F) / Onlykey (FIDO2) work right away. When I have access to my other FIDO2 device, I will test with a SOLO and Nitrokey FIDO2.
Could test it with Nitrokey FIDO 2 and could register it. It was difficult for the touch to register. I needed to ground myself first. Maybe it has todo with myself not properly grounded?
In general with the touch buttons you might need to make a short touch first to “reset” it, before making the actual gesture.
In the Nitrokey FIDO2 case you should see if the touch/tap is felt by the device due to the LED blinking being faster, before the touch gesture is accepted. There is no signals like that for the Nitrokey 3 at the moment.
Details:
Chrome: Version 101.0.4951.67 (Official Build) (64-bit)
I tested several browsers to rule out that maybe some plugin is interfering. I don’t usually use Chrome and the profile is empty.
I also verified on Arch with latest nitropy that I am using latest 1.0.3 firmware and that the PIN is correct by running the test suite. The PIN does not contain ambiguous characters where the keyboard layout might be an issue.
I was able to change and changeback the PIN on Windows using Settings->Sign-in Options->Security Key->Manage->Security Key PIN but it was necessary to unplug and insert the token.