# JSON Policy Deployment - Chrome

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2Fp09A6YMoBwirGYKpKG91%2FJSON%20Policy%20Deployment%20-%20Chrome.jpg?alt=media&#x26;token=a999e5fe-aa7d-4ece-b429-c4e05c3f5840" alt=""><figcaption></figcaption></figure>

## Deploying Keeper Chrome Browser Extension via JSON Policies

### Step 1: Create a Keeper JSON policy configuration file

1. If you currently do not have JSON Policy files created in which you want to utilize to deploy the Keeper Browser extension to all PCs in your organization, please proceed to creating your Keeper JSON policy file to your desired location, Ex: /tmp, and name it **keeperbe.json**

![Creating keeperbe.json file via Linux GUI](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LO5CAzpxoaEquZJBpYz%2F-MFqtcliQZqThhp8O7VU%2F-MFqu-kw78GjkIhO0PLw%2Flinux-keeperbe-pol.PNG?alt=media\&token=342455f9-e911-4045-bdbd-abda24e5f877)

**OR** create your **keeperbe.json** file via command-line

```
cd /tmp
touch keeperbe.json
```

2\. In your preferred JSON file editor or basic file editor, copy, paste and save the contents, below, into the **keeperbe.json** file or the policy file in which you currently utilize for your organization.

```
{
  "ExtensionSettings": {
    "bfogiafebfohielmmehodmfbbebbbpei": {
      "installation_mode": "force_installed",
      "update_url":
        "https://clients2.google.com/service/update2/crx"
    },
  }
}
```

### Step 2: Setup configuration folders

{% hint style="info" %}
If you currently have configuration folders setup for the user PCs in your organization, proceed to Step 3: Deploying the Keeper JSON Policy File.
{% endhint %}

On each PC, in your organization, that you would like to apply this policy on, you’ll need at least one folder to apply this policy.

1. If it does not already exist, create the directory structure, verbatim, as follows; `/etc/opt/chrome/policies/managed`and set the proper permissions for that directory.

![Creating managed policy directory via Linux GUI](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LO5CAzpxoaEquZJBpYz%2F-MFr2_HFdj9OHmEbv-W-%2F-MFr35MHCgFiBmh-vqUQ%2Flinux-managed.PNG?alt=media\&token=e17749e4-522e-4248-8ee3-62112f29cc40)

**OR** create your directory structure via command-line

```
mkdir /etc/opt/chrome/policies/managed
chmod -w /etc/opt/chrome/policies/managed
```

{% hint style="info" %}
The creation of this directory will most likely **NOT** be in the same directory as where Chrome is installed on the target Linux devices.  Ex:  My Chrome installed directory is /opt/google/chrome but my managed policy directory, in which my organization manages my Chrome install, is in the /etc/opt/chrome/policies/managed directory.
{% endhint %}

### Step 3: Deploying the Keeper JSON Policy File

Use your preferred method (utility or script) to push the **keeperbe.json** policy file and Chrome Browser to the target Linux devices in your organization.

* Push the **keeperbe.json** file to the `/etc/opt/chrome/policies/managed` directory on all target Linux devices in your network.
* Confirm that the files are in the correct directories on all the target Linux devices.

### Step 4: **Check Your Chrome Policies**

On a target client device, open Google Chrome and navigate to **chrome://policy** to see all policies that are applied.

![Successful KeeperFill Chrome Forced Install](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LO5CAzpxoaEquZJBpYz%2F-MFr5Vz7I3MybPcpoajr%2F-MFr64UKcU4fXcKPIJ_g%2Flinux-installed.PNG?alt=media\&token=5e31184e-ad87-4e88-b4b7-225c93d64741)

{% hint style="info" %}
You may need to select "Reload Policies" to apply this new policy to the target Linux devices.
{% endhint %}

![Reload Chrome Policies](https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LO5CAzpxoaEquZJBpYz%2F-MFr6e_GF2vnojzydt15%2F-MFr6x7iMcyt4WjVPnJi%2Flinux-reload.png?alt=media\&token=e94b48c1-30c8-428e-9d8a-bd4e6a1755db)

You may need to close and reopen Google Chrome before the new policies appear.