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
Create a passkey as 2FA on a supporting site (for example: github.com). Store the passkey in the browser, not BitWarden.
Log out of the site.
Log in to the site, invoking the BitWarden browser extension.
When prompted whether to use BitWarden to retrieve the passkey, choose Never.
Decide to use BitWarden after all (say, because iOS app support for passkeys has just been released :) and try to change the setting back to using BitWarden.
Expected Result
Editing the github.com entry in the macOS app has a visible setting for whether passkeys should be filled from BitWarden, and I can reset this to "always" or "ask each time". The same goes for the web interface.
Actual Result
I cannot find any way of changing this setting from "never" once it has been set.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
macOS 14.4.1 (23E224)
Installation method
Mac App Store
Build Version
2024.4.1 (23240)
Issue Tracking Info
I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
Expected Result
Editing the github.com entry in the macOS app has a visible setting for whether passkeys should be filled from BitWarden, and I can reset this to "always" or "ask each time". The same goes for the web interface.
Actual Result
I cannot find any way of changing this setting from "never" once it has been set.
Screenshots or Videos
No response
Additional Context
No response
Operating System
macOS
Operating System Version
macOS 14.4.1 (23E224)
Installation method
Mac App Store
Build Version
2024.4.1 (23240)
Issue Tracking Info
The text was updated successfully, but these errors were encountered: