Open Beeque opened 2 years ago
Replicated the issue on freshly installed Google Chrome browser as well. I think this was some issue with Windows Hello authentication. Toggling on and off "Enable browser integartion" and after multiple browser and app restarts it finally settled down and and asked the PIN code, and is now working as expected.
I thought this got fixed but it started again
Same problem using Google Chrome
Also experiencing this issue with Google Chrome. Interestingly, it only seems to affect my desktop, not my laptop.
My Desktop is: Windows 11 Pro, Version 21H2, Build 22000.778 Chrome Version 103.0.5060.66 Bitwarden Extension Version 2022.6.0 Bitwarden Desktop Version 2022.6.0
My Laptop is: Windows 11 Home, Version 21H2, Build 22000.739 Chrome Version 103.0.5060.66 Bitwarden Extension Version 2022.5.0 Bitwarden Desktop Version 2022.6.0
On my desktop, despite having Browser Integration enabled on the desktop program, the chrome extension does not see that browser integration is enabled.
Is it a bug with the 2022.6.0 extension?
Interestingly,Extension Version 2022.6.0 works well with Desktop Version 2022.5.1
2022.6.0 desktop app did not fix the issue for me. I installed latest Google Chrome, installed the extension, and when trying to enable biometrics I get the same error Browser Integration is not enabled
I'm on 2022.6.0 on Windows 11, and I'm using Brave version 1.40.109 (Chromium: 103.0.5060.66).
I'm also getting "Browser Integration is not enabled" despite toggling Browser Integration on/off many times in the Bitwarden desktop app, and then trying to enable it in the extension's settings. I've already allowed the extension in Incognito and to access file URLs.
I'm on a fresh install of Windows 10 Pro, and I'm using Chrome (Version 103.0.5060.114).
I'm having the same problem. I just did a fresh install of windows and installed the desktop app and the chrome extension. Even though I have biometrics enabled in the desktop app. The chrome extension still states that I haven't enabled it in the desktop application. I have tried re-installing chrome, the chrome extension, and the desktop app. Unfortunately, the apps won't pair.
I was getting this issue on 2022.6.0 on Windows 10, Firefox 102.0.1 (64 bit) but downgrading to 2022.5.1 fixed the problem. I have tried reinstalling multiple times and downgrading the bitwarden desktop client is the only thing that has worked so far.
Upgrading bitwarden from 2022.5.1 breaks the browser integration.
Desktop app versions 2022.6.1 and 2022.6.2 did not fix this yet. Full re-install on both desktop app and Edge browser extension. I noticed that having desktop app completely closed, the extension gives the same error. I think it should give another error when desktop app is not running.
For all the Chrome users experiencing this issue (Or browsers compatible with Chrome CRX extensions), here is a 5 minute workaround I found. I just did this on my desktop, with the BitWarden desktop application v2022.6.2
Steps 5-8 may not be necessary, that is just the specific process I went through, which worked for me.
Hopefully this helps someone else.
Hi everyone! I tried to replicate it with no luck. But I mark it as a bug in our internal tool to investigate it better and fix it as soon as we can.
It seems to be fixed on Windows 10 for Firefox on version 2022.8.0
Seems to be working for me too with the same version on Chrome / Win11
With the UWP Version of Firefox (on Win11) it is still not fixed, even with repeatedly toggling the setting on and off I can't get it working.
For the Firefox folks, perhaps this can help roll your extension version back to v2022.5.0 for the workaround I found?
For Edge/Chrome folks, please check the solution I was offered today in the issue #2679
Theo
For Edge/Chrome folks, please check the solution I was offered today in the issue #2679
Theo
Still can't get it to work.
This problem is also present in the Firefox extension on macOS, whereas Edge works just fine.
Does this warrant a separate issue?
For Edge/Chrome folks, please check the solution I was offered today in the issue #2679
Theo
Looks like I might be a bit late to the party, but this worked for me.
👍
Op ma 2 jan. 2023 04:20 schreef Justin San Agustin @.***
:
For Edge/Chrome folks, please check the solution I was offered today in the issue #2679 https://github.com/bitwarden/clients/issues/2679
Theo
Looks like I might be a bit late to the party, but this worked for me.
— Reply to this email directly, view it on GitHub https://github.com/bitwarden/clients/issues/2942#issuecomment-1368629607, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYRT6O5HRYHV7LWCHTND3GTWQJCQ3ANCNFSM5ZM5C7PQ . You are receiving this because you commented.Message ID: @.***>
I found a solution here
https://community.bitwarden.com/t/cant-enable-browser-extension-biometrics/16902/225
Edge: HKEY CURRENT USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts\com.8bit.bitwarden Mozilla: HKEY_CURRENT_USER\SOFTWARE\Mozilla\NativeMessagingHosts\com.8bit.bitwarden Chrome: HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.8bit.bitwarden
In this folder there is a "default" entry, double click In the value field, enter "C:\Users\YOURUSERNAME\AppData\Roaming\Bitwarden\browsers\firefox.json or chrome.json (Edge also uses chrome.json)
How can there be a 6 month old working solution without Bitwarden fixing the problem themselves?
The question is, where can you find the missing key in the uwp version of firefox?
Is this not going to be fixed? This feature is the reason I purchased Bitwarden premium.
The registry "fix" given above no longer works on the latest Windows 11 22H2 build.
I don't think this can be solved at all. For example, the method can't work with UWP browsers, because they don't have access to files outside their own.
Fix for Windows 11 22H2 and Edge or Chrome browser. No registry hack.
On Edge and Chrome, this solution worked for me. However, I had to add an additional step and go back into the manage extension and disable "All access to file URLs" as step 13. Then it worked as expected.
https://github.com/bitwarden/clients/issues/2679#issuecomment-1256969355
Steps To Reproduce
- Have Bitwarden desktop application running in the background, and logged in with Windows Hello (PIN code)
- Make sure that Enable browser integration is checked in desktop app settings.
- Microsoft Edge is closed. Open Microsoft Edge.
- Click Bitwarden browser extension
Expected Result
Log in using Windows Hello (PIN code) through the Bitwarden desktop application
Actual Result
Browser integration is not enabled in the Bitwarden Desktop application. Please enable it in the settings within the desktop application.
Screenshots or Videos
Additional Context
Other noteworthy application running: Bitdefender Total Security | Build 26.0.18.74 with default settings GlassWire Basic | Version 2.3.413
Operating System
Windows
Operating System Version
Windows 11 Version 21H2 ( OS Build 22000.739 )
Web Browser
Microsoft Edge
Browser Version
Version 102.0.1245.44 (Official build) (64-bit)
Build Version
2022.5.1
Can confirm this exact behavior with the latest version. The fix in my previous post immediately above does not work on this particular system. This issue seems to be system specific.
No fix despite this issue being reported by many users for a long time at this point does not inspire confidence. You would think that the Bitwarden developers would at least try to arrange some remote debugging sessions instead of constantly saying "Cannot replicate."
It is very important that you install and configure the Desktop application BEFORE installing and configuring the browser extension. That especially applies to enabling the browser extension integration within the desktop app BEFORE you install the browser extension.
It is very important that you install and configure the Desktop application BEFORE installing and configuring the browser extension. That especially applies to enabling the browser extension integration within the desktop app BEFORE you install the browser extension.
It only works sometimes. Hundreds of users have reported problems with biometrics even when they install the Desktop app and enable browser integration before installing the browser extension.
On one system I had to clean install Windows to get Bitwarden biometrics to work.
If you look back through the case history of this issue, it goes back years and Bitwarden engineering has not been able to fix it - probably because they cannot decisively figure out what things are causing the issues in the first place.
It is back for me after updating to Bitwarden desktop App v.2023.5.0. Dont update!
I just got a new Windows 11 desktop and laptop. These have plain vanilla installs of Windows 11. The first extension and the first program I install is BitWarden.
I used the "sideloaded" Desktop application.
On the laptop, browser integration works, but I get the "Enable Browser Integration" warning from the extension even though it's enabled.
I always install the desktop app first, check enable, and then install the extension.
I have no words on how annoying this bug is! We were going to pay for a Bitwarden license for the whole company, but because of the terrible support around Biometrics-usage in the Browser extension we stopped the order process.
Just to be very clear here: The biometrics-part always works fine with the Desktop app!
Only the communication from Bitwarden Browser extension to the Bitwarden Desktop App (and back) is not working as expected. How hard can it be, to add a debug-log to get this fixed?
Here a zipped Procmon-Protocol of that attempt to connect to the Desktop app: Bitwarden Chrome Extension fails to connect to Desktop App.zip
Notes: Just reading the developer-notes in some files like "ArchitectureSpecificRegistry.vbs" makes my cry. I can also see in Procmon, that changing the Browser extension attribute in the Desktop App is triggering the file "regPutValue.wsf" with only a single parameter "A" which is wrong based on the usage-notes inside that file.
Yeah! There's something very wrong here. I don't know why they don't acknowlege it. It doesn't work right on any of my Windows 11 machines.
Nobody there must care.
I uninstalled the browser extension (Chrome) and uninstalled the Windows app. Re-installed both and enabled all the biometrics and browser integration settings in the app first, then in the extension, and then everything worked. Took ten minutes.
It’s been my experience that this will work for a while and then break. I’ve given up on my machine. Most of the time it won’t work; one in 10 it does.
From: ken-cdit @.> Sent: Friday, October 27, 2023 7:51 AM To: bitwarden/clients @.> Cc: Robert Swirsky @.>; Comment @.> Subject: Re: [bitwarden/clients] Edge extension claims browser integration is not enabled, even that it is (Issue #2942)
I uninstalled the browser extension (Chrome) and uninstalled the Windows app. Re-installed both and enabled all the biometrics and browser integration settings in the app first, then in the extension, and then everything worked. Took ten minutes.
— Reply to this email directly, view it on GitHubhttps://github.com/bitwarden/clients/issues/2942#issuecomment-1783049510, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADDTWXFBXL67F4BWI6Z6AIDYBPC4HAVCNFSM5ZM5C7P2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZYGMYDIOJVGEYA. You are receiving this because you commented.Message ID: @.**@.>>
Fix for Windows 11 22H2 and Edge or Chrome browser. No registry hack.
On Edge and Chrome, this solution worked for me. However, I had to add an additional step and go back into the manage extension and disable "All access to file URLs" as step 13. Then it worked as expected.
Worked - thank you!
Bitwarden guys - it's a simple tweak to ask for additional permission for the browser extension
Bitwarden guys - it's a simple tweak to ask for additional permission for the browser extension
Not necessarily. I used the UWP Version of Firefox, so Bitwarden had no access to the files it needed. After I installed Firefox with WinGet everything worked like a charm.
Why the hack are there no log-files for troubleshooting?
It’s been my experience that this will work for a while and then break.
Many, many users have reported the same thing.
Bitwarden seems incapable of fixing, what should be, a showstopper for Bitwarden.
I have the same problem. Tried all solutions, wasted hours again, nothing works. First post regarding this problem I found online was from 3 years ago, when is it going to get fixed? I just got an email yesterday about a payment reminder for my subscription, so that seems to be working fine at least....
So sick and tired of having to deal with buggy software on a daily basis. Every day it's something else smh.
EDIT: Aaand browser integration has also stopped working on my other machines, yay.
Steps To Reproduce
Expected Result
Log in using Windows Hello (PIN code) through the Bitwarden desktop application
Actual Result
Browser integration is not enabled in the Bitwarden Desktop application. Please enable it in the settings within the desktop application.
Screenshots or Videos
Additional Context
Other noteworthy application running: Bitdefender Total Security | Build 26.0.18.74 with default settings GlassWire Basic | Version 2.3.413
Operating System
Windows
Operating System Version
Windows 11 Version 21H2 ( OS Build 22000.739 )
Web Browser
Microsoft Edge
Browser Version
Version 102.0.1245.44 (Official build) (64-bit)
Build Version
2022.5.1