When will the FireFox extension get biometric support now that I think it supports nativeMessaging

@kapitainsky Thank you for posting this… That worked great!

Sadly, no luck for me with this solution. I already had that folder in my Library path, including a bitwarden JSON settings file inside. I tried renaming the folder and then recreating it to see if that would help, but I still get the same error. :frowning:

But I am very glad to hear it has worked for others! Well done @kapitainsky!

what macOS you are on? Have you installed BW desktop app via App Store?

I am still on 10.14.6 (Mojave). And yes, the BW app was updated from the App Store.

Maybe it will only work on Big Sur?

Not too sure, but there was a GitHub issue for Catalina + Chrome, with similar error message: Issue with unlock with Biometrics (OSX Catalina, Brave, Chrome) · Issue #1709 · bitwarden/clients · GitHub

And a fix was added a couple days ago, but it doesn’t look like changes made it into 1.25.1.

In case you want to check if this is the issue you are seeing, try the workaround:

In the meantime manually creating the tmp directory inside ~/Library/Containers/com.bitwarden.desktop/Data should resolve the issue.

Since these error messages are very general, it is possible that your issue is caused by something else.

3 Likes

Hey @cho-m - THANK YOU! That actually worked! Awesome - I really appreciate the time that you took to investigate this and post a fix.

Worked for me! Thank you!

Biometric unlock working now! Windows 10 Pro 20H2, Firefox 87.0, Bitwarden Desktop App version 1.25.1, browser extension 1.49.1.

Seems to be working on Firefox and Chrome on pixel 3a with android 11.

How I’ve been waiting for this, and it’s great! Thanks BW team (and Mozilla I guess…)

Windows 10, Firefox 87.0, Bitwarden extension 1.49.1

WINDOWS 10: Still cannot get biometrics working with 1.49.1 in Firefox 78.9esr (which has been merged from Firefox 87).

Is there a patch needed to get this to work?
Is it a problem with the ESR release but not the mainline 87.0 release?
Is the fix tied to the most recent build of Windows (because I am necessarily using an older build)?

Help, please.

Same issue. I’d love to try this folder tip but I can’t find the correct directory in Windows 10.

As per BW release notes for 1.49.1:

Add support for browser biometrics on Firefox >= 87 (#1668)

So it does not work for older Firefox releases. Only version >=87 has required functionality.

ESR version of Firefox has frozen functionality and only “merges” security fixes from newer versions. If you have to use ESR it means that it will only work when Firefox 91 ESR is released.

1 Like

Ah, so that’s the problem. And I see now the policy here:

Extended Support Release (ESR) receives major updates on average every 42 weeks with minor updates such as crash fixes, security fixes and policy updates as needed, but at least every four weeks.

That’s unfortunate. And this means all other eagerly awaited Bitwarden improvements down the road will take a long time to come down to ESR versions. I think I will consider switching to the main FF channel.

Biometrics didn’t working for me until I removed and reinstalled the Bitwarden Firefox extension.

Mine still doesn’t work, tried reinstalling the extension, I’m still getting an error message telling me to enable Browser integration in Bitwarden desktop. Both firefox and extension are up-to-date.

Nevermind, fixed it. Disabled browser Integration in Desktop app, restart desktop app, re-enable Browser integration in Desktop app, I’m able to enable biometric support in Firefox now.

1 Like

Hello, will the Firefox extension support biometrics without having to open the main application first?

I noticed that Bitwarden recently added support for the Safari extension to do this, which is also documented here:

For all except Safari, the Bitwarden Desktop app must be logged in and running in order to use Unlock with Biometrics for a Browser Extension.

I’d love to see this feature come to extensions for other browsers such as Firefox, provided that the current lack of the feature is not due to technical limitations.