Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Bitwarden passkey works "unusual" with Bitwarden extension on Google Chrome #12583

Open
1 task done
tumatanquang opened this issue Dec 26, 2024 · 1 comment
Open
1 task done

Bitwarden passkey works "unusual" with Bitwarden extension on Google Chrome #12583

tumatanquang opened this issue Dec 26, 2024 · 1 comment
Labels
browser Browser Extension bug

Comments

@tumatanquang
Copy link

tumatanquang commented Dec 26, 2024 •
edited
Loading

Steps To Reproduce

  1. Use the latest version (currently 2024.12.3).
  2. Enable the "Make Bitwarden your default password manager" option.
  3. Visit webauthn.io
  4. Using both the "Register" and "Authenticate" functions will trigger the Chrome passkey instead of the Bitwarden passkey.

Expected Result

This will trigger the Bitwarden passkey pop-up.

Actual Result

It triggers Chrome passkey pop-up

Screenshots or Videos

bitwarden.mp4

The file fido2-content-script.js (and/or fido2-page-script.js) is no longer injected into the site

Additional Context

In previous versions (at least up to version 2024.11.2), the Bitwarden passkey pop-up still appeared occasionally, if the session did not appear Bitwarden passkey pop-up but Chrome passkey appeared, just restart the browser a few times, if lucky, it would continue to work.
However, from version 2024.12.3, it has completely stopped working. I tried:

  1. Delete the extension and then reinstall it.
  2. Delete all browser history, cookies,...
  3. Restart the browser.

But this feature still does not work.

According to some information I found, Bitwarden will inject the fido2-content-script.js (and/or fido2-page-script.js) file into the website, but when I check the website source code, I don't see these file(s) injected into the <head>. So, this could be the reason why Bitwarden passkey is not working?!

Operating System

Windows

Operating System Version

7

Web Browser

Chrome

Browser Version

109.0.5414.120

Build Version

2024.12.3

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.
@tumatanquang tumatanquang added browser Browser Extension bug labels Dec 26, 2024
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-16473

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
browser Browser Extension bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tumatanquang @bitwarden-bot