The Google Chrome browser supports configuration by policy. Policies can be used to centrally specify and manage many presettings for Chrome. The policy can be configured using a JSON file called chrome-mp.json can be implemented.
In TightGate-Pro, administrators can create and implement their own policy for Chrome at any time.
An overview of all available policies for the Chrome browser can be found here: https://chromeenterprise.google/policies/
To make it easier for our customers to work with a Chrome policy, we have provided a sample policy below:
| Name | Download name | MD5 |
|---|---|---|
| Chrome Policy | chrome-mp.json | md5sum |
The policy can be customised with a text editor before transferring it to TightGate-Pro.
Your policy must not contain the following values, as these are set dynamically by TightGate-Pro Server:
To adopt the policy in TightGate-Pro, please proceed as follows:
The Chrome browser ignores all content filtering rules set at TightGate-Pro. It is therefore not recommended to enable the Chrome browser for those identifiers that require content filtering.