I believe it could possible that this problem might actually be caused by trussed - the firmware "framework" both Solokeys and Nitrokeys are based off - in combination with...
This is not per-se an Forgejo bug (we use the recommended, [but more strict settings for WebAuthn](
db12ad17b9/modules...
After adding the key using Ungoogled Chromium, authenticating works on Firefox. So the issue can be isolated to registering a Security Key (Possibly only Nitrokeys, as @crystal reports that...
I tested adding the Nitrokey as Security key with Ungoogled Chromium too now.
It seems to work when using Ungoogled Chromium 115.0.5790.102 (Official Build, ungoogled-chromium).
So it seems to...
Hm, this appears to be a problem with the Nitrokey and recent versions of Firefox specifically. My Yubikey works as expected on Firefox 102 and Firefox 115.
My Nitrokey does however work on...
Same problem on next.forgejo.org:
Could not read your security key.
An unknown error occurred. Please retry.
Thus the problem also occurs on version 1.20.
@earl-warren Here is the environment I tested this with:
Context
- Browser: Firefox 115.0.2 (about:config security.webauthn.ctap2 set to true)
- Client OS: Fedora Silverblue 38.20230725 ...
@LeMoonStar could you please update the description with the latest information?
I am not the original creator of this issue, and thus cannot edit it.
I still experience the same error with version 1.20.1+0 via the latest docker image. I am trying to use a Nitrokey 3 which works perfectly on services like Google or GitHub. The problem is just...