Deployment via JumpCloud [MacOS]

Note:

  • This page applies to Google Chrome - on Mac computers only. It may be possible to deploy other configurations with JumpCloud.

  • For important additional information about deploying the extension, see Deploying the extension [Managed deployment].

This page includes:

About deployment via JumpCloud

This 3-step procedure describes how to use JumpCloud to deploy the browser extension for Google Chrome browsers - on Mac computers only.

The deployment procedure includes the following steps:

  • Step 1: Install the browser extension

  • Step 2: Connect the browser extension

  • Step 3: Activate the browser extension

For more information about deployment options, see Deploying the extension [Managed deployment].

Step 1: Install the browser extension

To perform Step 1, install the browser extension in the same way that you install other browser extensions.

Note:

  • It is recommended that you perform an installation procedure that will force-install the browser extension on all target devices so that users will not be able to remove or disable the browser extension.

  • The Perception Point browser extension is available in the Chrome Web Store.

  • The extension ID for the Perception Point browser extension is: kpehlcnleoaejbmmgncofcgpjnojlfbn

After you have installed the extension, you can verify that the installation was successful:

  1. Open a Google Chrome browser that has the extension installed.

  2. Click on the Perception Point browser extension icon, and then click the Settings icon [].

    Confirm that the user is signed-in - without having been prompted to sign-in.

Step 2: Connect the browser extension

Step 2 includes the following steps:

 

Step 2A: Download the Mac Shell script

Download the required Mac Shell script from the Advanced Browser Security console. The MacOS Shell script will contain the organization token that is required to deploy the extension without requiring any user input.

Step 2B: Deploy the organization token

Use JumpCloud to push the Mac Shell script that you downloaded in Step 2A - to all target endpoint devices. This will deploy the organization token on the target devices.

Step 2A: Download the Mac Shell script

To enable the browser extension to be activated without requiring any user input, you'll need to download a MacOS Shell script that includes the required organization token. You can download the MacOS Shell script from the Advanced Browser Security console. For details on how to download the required MacOS Shell script, see Downloading an organization token - making sure to select the MacOS option. you'll need this downloaded MacOS Shell script for use in Step 2B below.

Step 2B: Deploy the organization token

  1. Login to the JumpCloud administrator console.

  2. Open the Device Management > Commands page.

  3. In the top left corner of the Commands tab, click on the "+" button, and then select Command.

  4. In the New Command page > Details tab, enter:

    Details

    1. Name: Something like: MacOS - Organization Token

    2. Run As: root

    3. Type: Mac

    4. Command: Copy the contents of the MacOS Shell script file that you downloaded in Step 1A above, and paste the contents here.

      Launch Event

    5. Event: Run Manually

      Options

    6. Timeout After: 1200 seconds

    7. Time to Live (TTL) Settings: Use Smart Defaults: 10 days

  5. Click the Device Groups tab.

    Note: You can also open the Devices tab if your devices are not arranged in groups.

  6. Select the required group or groups [or devices].

  7. Click Save.

    Note: It is recommended that you test deployment of the token on a test device before performing a deployment in a production environment.

  8. To execute the deployment of the token, click Run Now on the right of the new command.

    This will deploy the token on all selected devices.

  9. To see the status, click the Results tab.

  10. To view the deployment logs, locate the new command, and then click View.

  11. Look for Success under Command Result Details.

Step 3: Activate the browser extension

For details, see Step 3: Activating the extension on endpoints.

See also: