Two things to bear in mind before enabling the integration are Permissions and Supportability, documented below: Permissions 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.īrowser extensions support the same biometrics options as desktop for Windows via Windows Hello using PIN, Facial Recognition, or other hardware that meets Windows Hello biometric requirements and for macOS via Touch ID. In practical terms, this means:įor all browser extensions, you will need to enable unlock with biometrics in desktop before proceeding. There are two settings to apply at the user level.ġ – Creating the personal folder in the TEMP folder:Ģ – Modification of environment variables:Īll you have to do is close and reopen the sessions to install the Chrome extensions without error.Unlock with biometrics is supported for extensions through an integration with the Bitwarden desktop app.

Modify TEMP and TMP environment variables.

For each user who logs in to create a personal folder in the C: TEMP folder.

Then you have to set up a GPO, which does two things: Solutionįirst, you must create on each RDS server, a TEMP folder at the root of the C with write / modify rights for everyone. I first tested the solution with an account made the changes by hand on the environment variables and I was able to install my Chrome extension. This error occurs when a user tries to install an extension on Google Chrome, I first think of a problem of right, with the admin account I got the same message, so I search on Google and I came across this article (in English) which explains why and how to solve it. In this article, I will explain how to resolve the COULD NOT GET TEMP DIRECTORY error simply.įrom my research this error appears on RDS (WS2012R2) servers using User Profile Disks (UPD).

Bitwarden plugin chrome