I have not been able to use my Windows Hello Camera for months already… where is this being tracked?
Apart from a few posts where users had problems setting this up, this is expected to work. Since a few weeks, I use it without any issues now. (though on my desktop only per Windows Hello PIN)
So, to look into it: Please post a screenshot of your Admin Dashboard first.
Okay, that’s the desktop app version. But I meant the Admin Dashboard of your self-hosted server.
Within the desktop app under the file menu, select “settings”. Within there is a checkbox, Unlock with Windows Hello. If checked, uncheck it and quit/restart bitwarden. Then, check it and let it re-integrate with Windows Hello.
If that does not do it, uninstall Bitwarden desktop app, remove the local storage and then reinstall the Bitwarden desktop app, followed by enabling Hello.
Also, it is necessary for Windows Hello to be able to unlock windows itself before you worry about making it work with apps, such as Bitwarden.
Ok, it works, but there is a bug:
- Close BW Windows desktop (App) and Chrome Extension window (Ext)
Start App, ensure that Windows Hello is available but do not Unlock- Open Ext and see that Windows Hello is available
- Close App, Windows Hello becomes unavailable in Ext
- Close the Ext, but leave Chrome running
- Start App, again, do not login
Open Ext again but Windows Hello is still unavailable- If I restart Chrome, Ext shows Windows Hello is available again
I should not have to restart Chrome in 8. If 4 can react and show unavailable, then 7 should also react and show available.
Two tiny details:
-
In step 2, it is necessary to login to your vault, but it is not necessary that the vault be unlocked (Understand Log In vs. Unlock). Without being logged in the desktop does not have the necessary cryptographic details to communicate with the extension.
-
In step 8, it is likely that disabling and reenabling the extension is sufficient.
Since the desktop app must remain running and logged in to support biometrics in the extension, you might consider the following settings in the desktop app:
- Timeout action
Lock - Unlock with Windows Hello
- Close to tray icon
- Start automatically on login
If you believe it to be a bug that the desktop app must be started before the browser extension is started, the proper place to file a bug report is on GitHub (click the green new issue button).
- I’m quite clear about
Log In, then lockvsLog In, then Log Out - If I have to D&E in step 8, why don’t I have to do the same D&E in step 4?
No, that is not what I describe the bug to be. The bug is: the Ext wrongly shows Windows Hello as unavailable and opening and closing the Ext does not rectify the problem.
If I restart Chrome, Ext now suddenly shows Windows Hello as available, without me touching the App.
From your GitHub issue:
It seems, you are using an unofficial server software, which is not supported by Bitwarden, as it is an independent product. From time to time, there will be compatibility issues between the official Bitwarden client apps (browser extension, mobile app, desktop app…) and an unofficial server product, when Bitwarden implements changes to its own server software and/or client apps. “…Bitwarden cannot guarantee that official clients will work perfectly with non-official servers.”
(Also due to this - and for other reasons - we recommend using the official Bitwarden server software.)
It is generally not possible for members of the Bitwarden community (users or developers) to help with such issues - and with issues of the unofficial server itself. Please seek support in their community spaces.
If you can replicate your issue on an official Bitwarden server, feel free to open a new thread here.
PS:
From my own experience on a BW server: the desktop app must always be started first – before even the browser gets started.
When you close the desktop app in step 4, but don’t close Chrome in step 5, then also starting the desktop app again in step 6 doesn’t work. Because: then technically, you started the desktop app after the browser – and then biometrics don’t work for the extension anymore.
Therefore again: the desktop app must always be started before even the browser is started. And best then, probably: never close the desktop app.
Good idea: check those five options above “Allow browser integration” in the desktop app settings:
