clients icon indicating copy to clipboard operation
clients copied to clipboard

Brave: Log in with passkey -> Verify with biometrics errors if browser extension is already unlocked

Open ethansaxenian opened this issue 1 year ago • 6 comments

Steps To Reproduce

  1. Ensure the browser extension is already unlocked
  2. Attempt to log into a website (e.g. https://community.bitwarden.com) with a passkey
  3. Click the Confirm button on the Log in with passkey? popup

Expected Result

I expect to be logged into the website via my saved passkey.

Actual Result

The popup displays an error: Could not complete biometrics.

Screenshots or Videos

screenshot

Additional Context

I can confirm that the Use master password option works as expected.

This error seemingly only occurs if the browser extension is already unlocked when I attempt to log in. If the extension is locked, I am prompted to unlock the vault using biometrics (which succeeds) before the Log in with passkey? popup is shown. Once I click Confirm I am logged in as expected.

Operating System

macOS

Operating System Version

Sonoma 14.3.1

Web Browser

Brave

Browser Version

1.67.119

Build Version

2024.6.2

Issue Tracking Info

  • [X] 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.

ethansaxenian avatar Jun 23 '24 16:06 ethansaxenian

I also encountered the same problem, using the passkey to log in. When verifying, if the browser extension has been unlocked, it prompts "Unable to complete biometrics". Error, please try again. At the same time, I confirm that using the master password to verify is OK, but if the browser extension is not unlocked, it can invoke the bitwarden desktop to complete the biometric verification.

Operating System Version:Windows 10 Version 22H2 Browser Version : Google Chrome 126.0.6478.115 Build Version :2024.6.2 PixPin_2024-06-24_14-32-53

githubzhuanyong avatar Jun 24 '24 06:06 githubzhuanyong

Same issue on both Firefox and Brave on macOS. Surprisingly, Safari is fine, likely due to the extension being an older one?

gokussjx avatar Jun 24 '24 19:06 gokussjx

Hello @ethansaxenian and everyone else,

Thank you all for your input. I was able to reproduce this behaviour and have flagged it to the Engineering department. Please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

This was reproduced with Bitwarden browser extension 2024.6.2 in Chrome 126.0 and Brave 1.67.119 on macOS 14.5, but Firefox 127.0.1 and Safari 17.5 worked as expected; On Windows 11 Pro 23H2, this was reproduced in Chrome 126.0 and Brave 1.67.119, but Firefox 127.0 and Edge 126.0 worked as expected.

@gokussjx, could you please check what version of Bitwarden browser extension and Firefox you're using? I was able to use Touch ID in order to use a passkey from my Bitwarden vault in testing within Firefox.

Thank you all again,

SergeantConfused avatar Jun 25 '24 10:06 SergeantConfused

Looks to be related to these PRs

https://github.com/bitwarden/clients/pull/8746 https://github.com/bitwarden/clients/pull/9734

Windows

Browser: Brave Version 1.67.119 Chromium: 126.0.6478.114 (Official Build) (64-bit) Extension version: 2024.6.2 image

Desktop App version: image

MacOS

Browser: Brave Version 1.67.119 Chromium: 126.0.6478.114 (Official Build) (arm64) Extension version: 2024.6.2 Desktop App version:


User Verification: Discouraged

Recording 2024-06-22 at 21 55 40

User Verification: Preferred

Recording 2024-06-22 at 21 57 19

just5ky avatar Jun 25 '24 14:06 just5ky

@SergeantConfused I'll amend my statement. I think I saw it occur a few times in Firefox, but can't reproduce it any more, hence, Brave is the only one having issues.

gokussjx avatar Jun 28 '24 05:06 gokussjx

@SergeantConfused I'll amend my statement. I think I saw it occur a few times in Firefox, but can't reproduce it any more, hence, Brave is the only one having issues.

It seems to be to only happening on Chrome Web Store version of the extension

TLDR: works fine in Firefox, Edge with edge web store extension instead of Chrome web store.

Here's the test that I conducted:

OS

  • Windows 11 IOT LTSC

Desktop App

image

Tested on webauthn.io with User Verification : Preferred

Browsers

  • Edge with Edge web store extension image

  • Edge with Chrome Web Store extension image

  • Chrome image

  • Brave image

  • Firefox image

just5ky avatar Jun 28 '24 08:06 just5ky

Same occuring in Chrome. Can confirm that "locking" chrome extension, then logging in with passkey works. If vault is unlocked, biometrics log in does not work. Can still use master password option.

motamedn avatar Jul 07 '24 17:07 motamedn

Same problem here. Chrome Extension 2024.6.2

martinjgrunwald avatar Jul 09 '24 11:07 martinjgrunwald

This is.... concerning. I too am having this issue on Vivaldi 6.8.3381.46 and Firefox 128.0 on linux mint 21.1. Passkeys have been wonky for months with BW. Locked out of several accounts at the moment...

tofr avatar Jul 10 '24 00:07 tofr

Yes can confirm this issue on Brave with extension Version: 2024.6.1

reubenyap avatar Jul 12 '24 06:07 reubenyap

@gbubemismith Are you aware of this?

bin101 avatar Jul 12 '24 07:07 bin101

@bin101, Thank you for bringing this to my attention. I would look into this

gbubemismith avatar Jul 12 '24 15:07 gbubemismith

Hello,

We had already documented this defect and verified that this pull request will address this issue.

This will be included in the next release candidate for our extensions. I cannot commit to a date for this yet, but I will close this ticket once released.

trmartin4 avatar Jul 12 '24 18:07 trmartin4

More authentication issues with Bitwarden.. Great. With everything that's already happening under issue #7150 and #9539 - I already feel a sense of regret that my annual subscription renewed last week.

alroberts avatar Jul 16 '24 18:07 alroberts

This issue was resolved with the 2024.7.1 release of the Bitwarden extension, which has been submitted to stores for approval and will be released as soon as approved by each store.

We are closing this issue, but please feel free to re-open or create a new issue if you continue to experience problems. We want to make sure that these frustrating issues can be identified and resolved as quickly as possible.

trmartin4 avatar Jul 27 '24 20:07 trmartin4