-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Cancelled passkey registration does not fall back to browser flow #2433
Comments
At least for me the browser fallbacks to the internal dialog when pressing cancel. Does it happen only when you have your hardware key connected? |
It happens both with the hardware key connected and disconnected. I stepped through it with Firefox' debugger, and it falls into this if-branch: The response is: (Sorry, I can't figure out a way to copy this from the devtools.) So the response is a valid object, albeit with an error code. |
Try disabling the fallback option and enable it back again? Otherwise this would need some debugging to see why the fallback doesn't happen at all. |
Enabling + disabling did not help. It seems to run until here:
Then it fails with |
That's strange. The |
I tried it on a spare laptop with a clean install of Kubuntu 24.10, Firefox 134.0.0 (snap), KeepassXC 2.7.9 (snap) and browser extension 1.9.5. There it works correctly. 🥲 I don't have time to do more digging right now, so I'll close this (and live with it, and maybe do a clean system install of my main laptop at some point). Ideally there would be more details in the error message as to WHY it's not allowed (but that's a Firefox issue, not a KeepassXC issue). I couldn't get more info out of the dev tools. :/ |
Alternatively you can try installing Firefox from a plain .tar.bz2 package and see if it behaves differently: |
When registering a new passkey, I cannot fall back to my physical hardware key when a KeepassXC database is open.
Steps to reproduce
Actual behaviour
The request is cancelled.
Expected behaviour
The request falls back to my browser's WebAuthn flow, so that I can register my hardware key.
Workaround
Metadata
The text was updated successfully, but these errors were encountered: