Deploy Browser Extensions using GPOs, Linux Policies, & .plist Files
When operating Bitwarden in a business setting, administrators may want to automate deployment of Bitwarden browser extensions to users with an endpoint management platform or group policy. This article will cover how to use GPOs and other templates to automate deployment of Bitwarden browser extensions to users with an endpoint management platform.
Deploying Bitwarden browser extensions to browsers on Windows generally require using Windows Group Policy to target managed computers an ADMX policy template. The procedure is slightly different for each browser:
To deploy the browser extension on Windows and Google Chrome:
Download and unzip the Chrome Enterprise Bundle for Windows.
From the unzipped directory:
Copy
\Configuration\admx\chrome.admx
toC:\Windows\PolicyDefinitions
Copy
\Configuration\admx\en-US\chrome.adml
toC:\Windows\PolicyDefinitions\en-US
Open the Windows Group Policy Manager and create a new GPO for Bitwarden browser extension installation.
Right-click on the new GPO and select Edit..., and proceed to navigate to Computer Configuration → Policies → Administrative Templates → Google Chrome → Extensions.
In the right-hand settings area, select Configure the list of force-installed apps and extensions. In the dialog, toggle the Enabled option.
Select the Show... button and add the following:
Bashnngceckbapebfimnlniiiahkandclblb;https://clients2.google.com/service/update2/crx
Click OK.
Still in ...Administrative Templates → Google Chrome, select Password manager from the file tree.
In the right-hand settings area, right-click Enable saving passwords to the password manager and select Edit. In the dialog, toggle the Disabled option and select OK.
Repeat Step 8 for the Enable Autofill for addresses and Enable Autofill for credit cards options, found in settings area for ...Administrative Templates → Google Chrome.
Apply the newly-configured GPO to your desired scope.
Deploying Bitwarden browser extensions to browsers on Linux generally involves using a .json
file to set configuration properties. The procedure is slightly different for each browser:
To deploy the browser extension on Linux and Google Chrome:
Download the Google Chrome .deb or .rpm for Linux.
Download the Chrome Enterprise Bundle.
Unzip the Enterprise Bundle (
GoogleChromeEnterpriseBundle64.zip
orGoogleChromeEnterpriseBundle32.zip
) and open the/Configuration
folder.Make a copy of the
master_preferences.json
(in Chrome 91+,initial_preferences.json
) and rename itmanaged_preferences.json
.Add the following to
managed_preferences.json
:Bash{ "policies:" { "ExtensionSettings": { "nngceckbapebfimnlniiiahkandclblb": { "installation_mode": "force_installed", "update_url": "https://clients2.google.com/service/update2/crx" } } } }
In this JSON object,
"nngceckbapebfimnlniiiahkandclblb"
is the application identifier for the Bitwarden browser extension. Similarly,"https://clients2.google.com/service/update2/crx"
signals Chrome to use the Chrome Web Store to retrieve the identified application.note
You may also configure forced installations using the ExtensionInstallForcelist policy, however the ExtensionSettings method will supersede ExtensionInstallForceList.
(Recommended) To disable Chrome's built-in password manager, add the following to
managed_preferences.json
inside of"policies": { }
:Bash{ "PasswordManagerEnabled": false }
Create the following directories if they do not already exist:
Bashmkdir /etc/opt/chrome/policies mkdir /etc/opt/chrome/policies/managed
Move
managed_preferences.json
into/etc/opt/chrome/policies/managed
.As you will need to deploy these files to users' machines, we recommend making sure only admins can write files in the
/managed
directory:Bashchmod -R 755 /etc/opt/chrome/policies
Using your preferred software distribution or MDM tool, deploy the following to users' machines:
Google Chrome Browser
/etc/opt/chrome/policies/managed/managed_preferences.json
tip
For more help, refer to Google's Chrome Browser Quick Start for Linux guide.
Deploying Bitwarden browser extensions to browsers on macOS generally involves using a property list (.plist
) file. The procedure is slightly different for each browser:
To deploy the browser extension on macOS & Google Chrome:
Download the Google Chrome .dmg or .pkg for macOS.
Download the Chrome Enterprise Bundle.
Unzip the Enterprise Bundle (
GoogleChromeEnterpriseBundle64.zip
orGoogleChromeEnterpriseBundle32.zip
).Open the
/Configuration/com.Google.Chrome.plist
file with any text editor.Add the following to the
.plist
file:Bash<key>ExtensionSettings</key> <dict> <key>nngceckbapebfimnlniiiahkandclblb</key> <dict> <key>installation_mode</key> <string>force_installed</string> <key>update_url</key> <string>https://clients2.google.com/service/update2/crx</string> </dict> </dict>
In this codeblock,
nngceckbapebfimnlniiiahkandclblb
is the application identifier for the Bitwarden browser extension. Similarly,https://clients2.google.com/service/update2/crx
signals Chrome to use the Chrome Web Store to retrieve the identified application.note
You may also configure forced installations using the ExtensionInstallForcelist policy, however the ExtensionSettings method will supersede ExtensionInstallForceList.
(Recommended) To disable Chrome's built-in password manager, add the following to
com.Google.Chrome.plist
:Bash<key>PasswordManagerEnabled</key> <false />
Convert the
com.Google.Chrome.plist
file to a configuration profile using a conversion tool like mcxToProfile.Deploy the Chrome
.dmg
or.pkg
and the configuration profile using your software distribution or MDM tool to all managed computers.
tip
For more help, refer to Google's Chrome Browser Quick Start for Mac guide.
Suggest changes to this page
How can we improve this page for you?
For technical, billing, and product questions, please contact support