Admin ConsoleDeploy Client Apps

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.

Windows

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:

  1. Download and unzip the Chrome Enterprise Bundle for Windows.

  2. From the unzipped directory:

    • Copy \Configuration\admx\chrome.admx to C:\Windows\PolicyDefinitions

    • Copy \Configuration\admx\en-US\chrome.adml to C:\Windows\PolicyDefinitions\en-US

  3. Open the Windows Group Policy Manager and create a new GPO for Bitwarden browser extension installation.

  4. Right-click on the new GPO and select Edit..., and proceed to navigate to Computer ConfigurationPoliciesAdministrative TemplatesGoogle ChromeExtensions.

  5. In the right-hand settings area, select Configure the list of force-installed apps and extensions. In the dialog, toggle the Enabled option.

  6. Select the Show... button and add the following:

    Bash
    nngceckbapebfimnlniiiahkandclblb;https://clients2.google.com/service/update2/crx

    Click OK.

  7. Still in ...Administrative TemplatesGoogle Chrome, select Password manager from the file tree.

  8. 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.

  9. Repeat Step 8 for the Enable Autofill for addresses and Enable Autofill for credit cards options, found in settings area for ...Administrative TemplatesGoogle Chrome.

  10. Apply the newly-configured GPO to your desired scope.

Linux

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:

  1. Download the Google Chrome .deb or .rpm for Linux.

  2. Download the Chrome Enterprise Bundle.

  3. Unzip the Enterprise Bundle (GoogleChromeEnterpriseBundle64.zip or GoogleChromeEnterpriseBundle32.zip) and open the /Configuration folder.

  4. Make a copy of the master_preferences.json (in Chrome 91+, initial_preferences.json) and rename it managed_preferences.json.

  5. 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.

  6. (Recommended) To disable Chrome's built-in password manager, add the following to managed_preferences.json inside of "policies": { }:

    Bash
    { "PasswordManagerEnabled": false }
  7. Create the following directories if they do not already exist:

    Bash
    mkdir /etc/opt/chrome/policies mkdir /etc/opt/chrome/policies/managed
  8. Move managed_preferences.json into /etc/opt/chrome/policies/managed.

  9. As you will need to deploy these files to users' machines, we recommend making sure only admins can write files in the /managed directory:

    Bash
    chmod -R 755 /etc/opt/chrome/policies
  10. 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.

MacOS

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:

  1. Download the Google Chrome .dmg or .pkg for macOS.

  2. Download the Chrome Enterprise Bundle.

  3. Unzip the Enterprise Bundle (GoogleChromeEnterpriseBundle64.zip or GoogleChromeEnterpriseBundle32.zip).

  4. Open the /Configuration/com.Google.Chrome.plist file with any text editor.

  5. 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.

  6. (Recommended) To disable Chrome's built-in password manager, add the following to com.Google.Chrome.plist:

    Bash
    <key>PasswordManagerEnabled</key> <false />
  7. Convert the com.Google.Chrome.plist file to a configuration profile using a conversion tool like mcxToProfile.

  8. 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