With Cerby, you can deploy the Cerby browser extension across all of your company endpoints using a Mobile Device Management (MDM) service and a configuration file.
Safari
Microsoft Edge
Mozilla Firefox
Google Chrome
To set up the deployment and payloads for the four web browsers, you can use a device management platform such as Jamf (MacOS) or Tanium (Windows); then release the payloads to all the intended devices.
This article describes the process to achieve a seamless installation and ensure a consistent user experience.
MacOS
The deployment setup on MacOS endpoints is different depending on the web browser:
The following sections describe the setup process for each browser.
Safari
The deployment setup for Safari is done via an app assignment through Apple Business Manager using a location token integrated with your MDM service.
When you complete the setup, you can select the Cerby browser extension from the App Store to include it in any configuration profiles, blueprints, or payloads within your MDM system.
Requirements
The following are the requirements to set up the deployment:
An Apple Business Manager account with the Content Manager role (minimum)
Access to an MDM service with the necessary permissions to create and deploy configuration profiles and their payloads
Deployment setup
To set up the deployment and payloads of the Cerby browser extension, you must complete the following steps:
Log in to your Apple Business Manager account.
Select the Apps or Apps and Books option from the left navigation drawer to open a page with a list of assigned apps.
Click the Store button located below the search bar.
Click the View Store button located in the right pane. The Store page is displayed.
Search for the Cerby Web Extension app and select it. The app license details are displayed on the right pane, as shown in Figure 1.
Figure 1. Cerby Web Extension license details on the Store page
Select the corresponding location token to assign to your MDM service from the Assign to drop-down list.
Enter the number of licenses you want to make available for deployment through your MDM service in the Quantity field.
Click the Buy or Get button. The Store page closes.
Now you are done with the setup for Safari. The Cerby browser extension will be displayed in the App Store Apps section of your MDM’s library, and you can now include the extension in any of your configuration profiles, blueprints, or payloads.
Firefox
The deployment setup for Firefox is done via a computer configuration profile and payload that you must configure in Jamf Pro using a custom JSON schema manifest provided by Cerby.
After the setup, Jamf Pro will distribute the configuration and payload according to the distribution method and target endpoints you define, and the Cerby browser extension will be installed automatically.
For more information on customizing an app using Jamf Pro, read the Technical Paper: Managing Settings for Computer Applications using JSON Schema and Jamf Pro 10.26.0 or Later official documentation.
Deployment setup
To set up the configuration file, payload, deployment, and roll out the installation, you must complete the following steps:
Log in to your Jamf Pro account.
Click the Computers button located at the top of the left navigation drawer.
Select the Configuration Profiles option from the CONTENT MANAGEMENT section in the left navigation drawer. The Configuration Profiles page is displayed.
Create a new configuration profile by performing the following actions:
Click the New button. The General section of the Options tab is displayed in the New MacOS Configuration Profile page.
Enter and select the corresponding configuration profile details in the General section. The fields are the following:
Name
Enter Cerby Firefox Web Extension in the Name field.
Description
Category
Level
Distribution Method
Enter the JSON schema manifest to populate the configuration properties by performing the following actions:
Select the External Applications option from the Application & Custom Settings drop-down list located in the left pane of the page. The External Applications section is displayed.
Click the Add button. The Source drop-down list is displayed.
Select the Custom Schema option from the Source drop-down list. The Preference Domain field and Custom Schema section are displayed.
Enter org.mozilla.firefox in the Preference Domain field.
Click the Add schema button. The Custom JSON Schema dialog box is displayed.
Copy the following JSON schema and paste it in the Custom Schema field:
{
"$schema": "http://json-schema.org/schema#",
"title": "org.mozilla.firefox",
"definitions": {
"extension": {
"type": "object",
"title": "Extension",
"properties": {
"installation_mode": {
"type": "string",
"title": "Installation Mode",
"default": "force_installed",
"enum": ["allowed", "blocked", "force_installed", "normal_installed"]
},
"install_url": {
"type": "string",
"description": "The location of the extension to be installed.",
"title": "Install URL"
},
"install_sources": {
"type": "array",
"title": "Install Sources",
"items": {"type": "string", "title": "URL"}
},
"blocked_install_message": {
"type": "string",
"title": "Blocked Install Message",
"description": "Error message to display to users if they're blocked from installing an extension."
}
}
}
},
"type": "object",
"properties": {
"ExtensionUpdate": { "type": "boolean", "title": "Allow Extension Updates", "default": "false" },
"ExtensionSettings":{
"type": "array",
"title": "Extension Settings",
"items": [{
"type": "object",
"title": "Extension",
"properties": {
"*": {
"type": "object",
"title": "All Extensions",
"properties": {
"blocked_install_message": {
"type": "string",
"title": "Blocked Install Message",
"default": "Custom error message"
},
"install_sources": {
"type": "array",
"title": "Install Source URLs",
"items": {"type": "string", "title": "URL"},
"default": ["https://addons.mozilla.org/"]
},
"installation_mode": {
"type": "string",
"title": "Installation Mode",
"default": "blocked",
"enum": ["allowed", "blocked", "force_installed", "normal_installed"]
},
"allowed_types": {
"type": "array",
"title": "Allowed Types",
"items": {"type": "string", "enum": ["extension", "theme", "dictionary", "langpack"]}
}
}
}
}
}],
"additionalItems": {"$ref": "#/definitions/extension"}
},
"EnterprisePoliciesEnabled": { "type": "boolean", "title": "Enable Enterprise Policies", "description": "Enable policy support on macOS.", "default": "false" },
"Extensions":{
"type": "object",
"title": "Extensions",
"properties": {
"Install": {
"type": "array",
"title": "Install",
"items": {"type": "string", "title": "URL"},
"default": ["https://addons.mozilla.org/firefox/downloads/latest/cerby-s-browser-extension/addon-16690455-latest.xpi"]
},
"Uninstall": {
"type": "array",
"title": "Uninstall",
"items": {"type": "string", "title": "Extension ID"},
"default": []
},
"Locked":
{
"type": "array",
"title": "Locked",
"items": {"type": "string", "title": "Extension ID"},
"default": ["{f961ea35-985c-412d-9b06-aafd75752587}"]
}
}
}
}
}Click the Save button. The dialog box closes, and the Preference Domain Properties section is displayed with information pre-filled.
Verify that the values in the following fields were pre-filled correctly:
Extensions > Install > URL 1: https://addons.mozilla.org/firefox/downloads/latest/cerby-s-browser-extension/addon-16690455-latest.xpi
Extensions > Locked > Extension ID 1: {f961ea35-985c-412d-9b06-aafd75752587}
Activate the Scope tab to add your deployment targets. For more information, read the Scope official documentation.
Click the Save button located at the bottom right of the page.
Now you are done. The MacOS endpoints will install the Cerby browser extension automatically according to the distribution method.
Figure 2 shows how the Cerby browser extension is displayed on the extension management page of a MacOS computer using Firefox.
Figure 2. Cerby browser extension in the Manage Your Extensions page of the Firefox web browser
IMPORTANT: The deployment setup for Firefox blocks the users from uninstalling or disabling the Cerby browser extension.
Chrome
The deployment setup for Chrome is done via a computer configuration profile and payload that you must configure in Jamf Pro using a custom JSON schema manifest provided by Cerby.
After the setup, Jamf Pro will distribute the configuration and payload according to the distribution method and target endpoints you define, and the Cerby browser extension will be installed automatically.
For more information on customizing an app using Jamf Pro, read the Technical Paper: Managing Settings for Computer Applications using JSON Schema and Jamf Pro 10.26.0 or Later official documentation.
Deployment setup
To set up the configuration file, payload, deployment, and roll out the installation, you must complete the following steps:
Log in to your Jamf Pro account.
Click the Computers button located at the top of the left navigation drawer.
Select the Configuration Profiles option from the CONTENT MANAGEMENT section in the left navigation drawer. The Configuration Profiles page is displayed.
Create a new configuration profile by performing the following actions:
Click the New button. The General section of the Options tab is displayed in the New MacOS Configuration Profile page.
Enter and select the corresponding configuration profile details in the General section. The fields are the following:
Name
Enter Cerby Google Chrome Web Extension in the Name field.
Description
Category
Level
Distribution Method
Enter the JSON schema manifest to populate the configuration properties by performing the following actions:
Select the External Applications option from the Application & Custom Settings drop-down list located in the left pane of the page. The External Applications section is displayed.
Click the Add button. The Source drop-down list is displayed.
Select the Custom Schema option from the Source drop-down list. The Preference Domain field and Custom Schema section are displayed.
Enter com.google.Chrome in the Preference Domain field.
Click the Add schema button. The Custom JSON Schema dialog box is displayed.
Copy the following JSON schema and paste it in the Custom Schema field:
{
"title": "Cerby Google Chrome Extensions (com.google.Chrome)",
"description": "Install Cerby Web Extenion in Google Chrome",
"properties": {
"ExtensionInstallForcelist": {
"title": "Extension Install Forcelist",
"description": "Cerby Chrome Web Extension",
"property_order": 5,
"type": "array",
"items": {
"title": "Extension ID",
"default": "clccplmaaeihbagbefjinmclielobnkb;https://clients2.google.com/service/update2/crx",
"type": "string"
}
}
}
}Click the Save button. The dialog box closes, and the Preference Domain Properties section is displayed with information pre-filled.
Verify that the value in the following field was pre-filled correctly:
Extension Install Forcelist > Extension ID 1: clccplmaaeihbagbefjinmclielobnkb;https://clients2.google.com/service/update2/crx
Activate the Scope tab to add your deployment targets. For more information, read the Scope official documentation.
Click the Save button located at the bottom right of the page.
Now you are done. The MacOS endpoints will install the Cerby browser extension automatically according to the distribution method.
Figure 3 shows how the Cerby browser extension is displayed on the extension management page of a MacOS computer using Chrome.
Figure 3. Cerby browser extension in the Extension page of the Chrome web browser
IMPORTANT: The deployment setup for Chrome blocks the users from uninstalling or disabling the Cerby browser extension.
Windows
The deployment setup on Windows endpoints for Chrome, Edge, and Firefox is done via a PowerShell script provided by Cerby that you must upload to a configuration profile or payload.
When the script runs with a command (also provided by Cerby) in your selected endpoints, the Cerby browser extension is installed.
Requirements
The following are the requirements to set up the deployment and perform the enterprise rollout:
The
cerby_browser_extensions.ps1file, available for download in this articleAn MDM service for Windows, such as Intune, Hexnode, Tanium, or ManageEngine, in which you can create a configuration profile or payload to upload the script and set up an execution command
IMPORTANT: The deployment of a PowerShell script depends on your MDM’s capabilities. For more setup information, you can read the official documentation from the following providers:
Deployment setup
To set up the deployment, upload the script, set up the execution command, and roll out the installation, you must complete the following steps:
Log in to your MDM service for Windows.
Create a configuration profile or payload.
Set up a custom script deployment. The setup involves the following actions:
Upload the
cerby_browser_extensions.ps1file to the configuration profile or payload.Specify the following as the command to run the script:
powershell.exe -ExecutionPolicy Bypass -WindowStyle Hidden -Noninteractive -NoProfile .\cerby_browser_extensions.ps1
Select the device groups or specific devices to which the Cerby browser extension must be installed.
Now you are done. All the Windows endpoints will execute the command to install the Cerby browser extension on their next MDM check-in.
Downloadable file
The following is the file you need for the deployment setup on Windows endpoints: