You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to 1Passwords behaviour if the register button is clicked on webauthn.io it should trigger the popup from KeepassXC
Current Behavior
On MacOS or any other device that supports passkeys natively the browser hijacks control of the Passkey setup/login, and if you click cancel on it the request fails as it was denied
Possible Solution
1Password and other extensions seem to be getting the notification/trigger regardless of other installed webauthn/passkey providers
There's no logs in the console for the extension page/background script, but the extension is loaded and connected, I'm just assuming that the issue is that the browser is beating the extension to it, there also doesn't seem to be a way to turn off the default browser passkey support to validate this :(
The text was updated successfully, but these errors were encountered:
agnosticlines
changed the title
Passkeys/Webauthn support broken on mac or if another authenticator device is present (?)
Passkeys/Webauthn support broken on Mac or if another authenticator device is present (?)
Feb 22, 2024
Expected Behavior
Similar to 1Passwords behaviour if the register button is clicked on webauthn.io it should trigger the popup from KeepassXC
Current Behavior
On MacOS or any other device that supports passkeys natively the browser hijacks control of the Passkey setup/login, and if you click cancel on it the request fails as it was denied
Possible Solution
1Password and other extensions seem to be getting the notification/trigger regardless of other installed webauthn/passkey providers
Steps to Reproduce (for bugs)
Debug info
KeePassXC - 2.8.0-snapshot
KeePassXC-Browser - 1.8.12
Operating system: Mac
Browser: Chrome/Edge
There's no logs in the console for the extension page/background script, but the extension is loaded and connected, I'm just assuming that the issue is that the browser is beating the extension to it, there also doesn't seem to be a way to turn off the default browser passkey support to validate this :(
The text was updated successfully, but these errors were encountered: