30

Same here - using the Chrome extension but the behaviour is the same with Firefox as well. When attempting to enable biometrics, it starts the communication with the desktop app but then disappears just before the touch id popup appears. Clicking on the touch id popup, there is now no response from the extension as it has "closed" and I need to put my master password in again. I don't know if the extension is crashing/reloading or whatever. I tried putting vault timeout to never at both sides temporarily and whilst that takes away the re-entering of the master password it still never sets up touch id.

    There’s a great post on this but I couldn’t find it. I started from scratch had the same problem. In desktop Bitwarden preferences, I unchecked Allow browser integration and rechecked it and set up Touch ID again successfully. Another method that worked was setting up Unlock with PIN and then setting up Unlock with biometrics. I then disabled Unlock with PIN.

      Thanks - by fiddling with that setting and bit of back and forth I finally managed to get it to work. Wasn't straight forward though.

        3 months later

        it is working ✅
        i just need to check Allow browser integration option in Bitwarden Mac App.

        19 days later

        Hi guys, I discoverd Orion today and I already like it !

        The only thing that I didn't like was that the Bitwarden extension didn't worked with biometrics but it was quickly solved with the file trick thanks to @sbeaz.

        HOWEVER, the com.8bit.bitwarden.json file was not in
        ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/
        but in ~/Library/Application\ Support/Google/Mozilla/NativeMessagingHosts/.
        I don't know why it was there (maybe cause I have never had Chrome on my mac) but when I placed it in
        ~/Library/Application\ Support/Orion/NativeMessagingHosts/ it worked with the Chrome AND the Firefox extensions.

        Hope this could help someone

        2 months later

        After adding the com.8bit.bitwarden.json file to ~/Library/Application\ Support/Orion/NativeMessagingHosts/ the Bitwarden extension, both Firefox and Chrome is asking to "Start the bitwarden application" however the app is already running and unlocked in the background

          7 months later

          The workaround above did not work for me as i did not have a Google folder within application support. Perhaps as i had never installed a google app on the machine before, including chrome. I just had safari, bitwarden app store app, and orion.

          My solution involved:

          i can't say for sure if each step is necessary im afraid

          after this, the com.8bit.bitwarden.json was already in the right place, so I didn't have to perform the workarounds mentioned above.

          i only needed to enable browser integration & touch id in bitwarden mac app, log into orion extension, enable touch id, and i got a system prompt (you might need to log in 1 more time before it works)

          ps i have "require verification for browser integration" unchecked in bitwarden app settings

          hope this helps

            Not sure what we can do. I really do not like the idea of having a popup that comes up as users install an extension. Can you as Bitwarden users write to them and ask them to support this natively?

              Vlad I don’t know if there’s any thing you can do. I will think on and about it, but nothing comes to mind right now.

                a month later

                Latest RC
                Bitwarden biometrics authentication is still not working, no pop-up shows on screen for touch-id.
                Leaving a screen record here on streamable

                • Vlad replied to this.

                  Vlad no I have not, that's not a viable solution: it might as well fix it but the issue is still there for regular users who don't want headaches for fixing things manually. Mass adoption requires the software to work natively: imo it's bad user experience if you have to download other softwares, dig into config files and do all that crap manual thing just to get an extension to work properly.
                  However, the main reason I haven't tried that out is what brought me to Orion: I want my laptop to never see Chromium-based browsers again (for those who want to investigate)

                    heisznberg The main point is that Orion can noy change another app's behaviour (which is need for this to work, Bitwarden does not acknowledge Orion's existence). But Bitwarden users could ask Bitwarden team / community to support Orion, similar how 1Password community got it to support Orion.

                    4 months later

                    cooloodoo The real mess here is that a Chrome browser has to be installed. Why is this a mess: beause it shows that Orion ability to use and install Firefox or Chrome extensions DOES NOT ACTUALLY WORK. Orion downloads the extension code; adds it to whatever metadata Orion maintains for extensions it has installed. It can run. But this necessary file for communication between the Bitwarden extension and the Bitwarden desktop file will not be present, as cooloodoo has proven.

                    The only viable workaround is to install a Chrome based browser first. Otherwise the needed file CANNOT be present.

                    It's ok to have bugs; it is divine to admit it; it is Divinity raised to a higher power (double entendre intended) to fix them (even if there is a goofy workaround--and it would help to correctly document said workaround as cooloodoo has done).

                    It is not that easy to get the extension working with Chrome and communicating with the desktop app. Install extension. Manage extension. Enable extension. Launch extension. Change setting to use biometrics in extension. Get prompted for password or finger to open running instance of extension. Yay, it works.

                    Then copy com.8bit.bitwarden.json to the folder noted above for Orion bitwarden application support. Go through the rigamorole to turn on biometric verification. On the third attempt the connection to the desktop Bitwarden occurs and the setting "sticks" in the extension.

                    Whether this is Bitwarden's fault or Orion's, it is a mess. One is inclined to say that it is Orion's fault because the process to enable biometric unlock for the extension works on Safari, Firefox or a Chromium based browser. The problem would seem to be as simple as Orion not installing the Chrome plugin correctly--so the process of accessing and installing "foreign" extensions--which is a great benefit (even it probably can't ever work for every extenstion, which is understandable)--still needs some work. The challenge will be that this work might be extension specific--I hope it is possible to do this w/o per extension work.

                    In any case, thanks to cooloodoo I have it working. For clarity I note that installing the Chrome Bitwarden extension from within Orion does NOT download the required file in the correct place--this is really the only actual problem.

                      No one is typing