Skip to main content

Deploy the Nudge Security Browser Extension to MacOS through Jamf

A guide for Jamf customers to deploy the Nudge Security Browser Extension to MacOS devices.

Velizar Demirev avatar
Written by Velizar Demirev
Updated over a week ago

Existing force-installed extensions

Follow these instructions if you already have an extension force install list for Chrome, Edge, or other Chromium-based browsers. Be sure to use the same force-install list for each browser to prevent policy conflicts during deployment.

  1. In JAMF, go to the existing Configuration Profile for the browsers where you have existing force-install lists.

  2. In Custom Settings, add the Nudge extension ID and update URL to the existing force-install list for that browser:

    1. For all Chromium-based browsers (Chrome, Edge, Brave, etc.,) add the following:

      1. Extension ID:diaecjfdpohehjhliaephjnpnlmeajfa

      2. Update URL: [https://clients2.google.com/service/update2/crx](<https://clients2.google.com/service/update2/crx>);

    2. For Firefox, add the following:

      1. Extension ID: nudge-security-browser-helper@nudge.security

      2. Update URL: https://addons.mozilla.org/firefox/downloads/latest/nudge-security-browser-helper/latest.xpi

  3. Save your changes.

  4. Create a new Configuration Profile to configure the deployment policy for the Nudge Security Browser Extension.

  5. Name your Configuration Profile (i.e. Nudge Install Chrome MacOS)

  6. In the new Configuration Profile, scroll down and select Custom Settings.

  7. Set preference domain to: com.google.Chrome.extensions.diaecjfdpohehjhliaephjnpnlmeajfa

  8. Head to Nudge Security and get the deployment policy PLIST file by going to Settings → Browser Extension → Enroll New Users → Managed Deployment → Device Management → select your browser → MacOS. Download the PLIST file in Step 2 of the instructions. In that PLIST, look for the deployment key field and copy it.

  9. Replace the string DEPLOYMENT_KEY_HERE with your key copied from Nudge Security earlier. Copy and paste PLIST linked below:

<dict> 	<key>nudge-security-deployment-key</key> 		<string>deployment key here</string> </dict>

Finally, save the policy.

New deployments

If this is your first time force-installing a browser extension through Jamf, follow the instructions below. At a high level, you’ll need to:

  • Create individual configuration profiles for each browser type to install the browser extension.

  • Create an additional configuration profile for each browser type to configure the deployment policy. (E.g. Chrome will require a config profile for installation and another for the deployment policy.)

  • Verify that the installation and policy configuration were successful.

Important note: Create one policy per browser type. Do not combine multiple browser types in one policy.

Chrome

  1. Go to Configuration Profiles → New to create a new install policy.

  2. Name your Configuration Profile (i.e. Nudge Install Chrome MacOS).

  3. On the left-nav, scroll down and select Custom Settings.

  4. Click configure and set your preference domain to com.google.Chrome

  5. In the text box (or upload field), insert your PLIST code below to install the extension:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict>  <key>ExtensionInstallForcelist</key>  <array>   <string>diaecjfdpohehjhliaephjnpnlmeajfa</string>  </array> </dict>

  1. Save the policy.

  2. Create a new Configuration Profile to configure the deployment policy for the Nudge Browser Extension.

  3. Name your Configuration Profile (i.e. Nudge Configure Chrome MacOS).

  4. In the new Configuration Profile, scroll down and select Custom Settings.

  5. Set preference domain to: com.google.Chrome.extensions.diaecjfdpohehjhliaephjnpnlmeajfa

  6. Head to Nudge Security and find the deployment policy PLIST file by going to Settings → Browser Extension → Enroll New Users → Managed Deployment → Device Management → select your browser → MacOS. Download the PLIST file in Step 2 of the instructions. In that PLIST, look for the deployment key field and copy.

  7. Replace the string DEPLOYMENT_KEY_HERE with your key copied from Nudge Security earlier. Copy and paste PLIST linked below:

<dict> 	<key>nudge-security-deployment-key</key> 		<string>deployment key here</string> </dict>

Finally, save the policy.

Edge

  1. Go to Configuration Profiles → New to create a new install policy.

  2. Name your Configuration Profile (i.e. Nudge Install Edge MacOS).

  3. On the left-nav, scroll down and select Custom Settings.

  4. Click configure and set your preference domain to com.microsoft.Edge

  5. In the text box (or upload field), insert your PLIST code below to install the extension:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict>  <key>ExtensionInstallForcelist</key>  <array>   <string>diaecjfdpohehjhliaephjnpnlmeajfa</string>  </array> </dict>

  1. Save the policy.

  2. Create a new Configuration Profile to configure the deployment policy for the Nudge Browser Extension.

  3. Name your Configuration Profile (i.e. Nudge Configure Edge MacOS).

  4. In the new Configuration Profile, scroll down and select Custom Settings.

  5. Set preference domain to: com.microsoft.Edge.extensions.diaecjfdpohehjhliaephjnpnlmeajfa

  6. Head to the Nudge Security and grab the deployment policy PLIST file by going to Settings → Browser Extension → Enroll New Users → Managed Deployment → Device Management → select your browser → MacOS. Download the PLIST file in Step 2 of the instructions. In that PLIST, look for the deployment key field and copy.

  7. Replace the string DEPLOYMENT_KEY_HERE with your key copied from Nudge Security earlier. Copy and paste PLIST linked below:

<dict> 	<key>nudge-security-deployment-key</key> 		<string>deployment key here</string> </dict>

Finally, save the policy.

Brave

  1. Go to Configuration Profiles → New to create a new install policy.

  2. Name your Configuration Profile (i.e. Nudge Install Brave MacOS).

  3. On the left-nav, scroll down and select Custom Settings.

  4. Click configure and set your preference domain to com.brave.Browser

  5. In the text box (or upload field), insert your PLIST code below to install the extension:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict>  <key>ExtensionInstallForcelist</key>  <array>   <string>diaecjfdpohehjhliaephjnpnlmeajfa</string>  </array> </dict>

  1. Save the policy.

  2. Create a new Configuration Profile to configure the deployment policy for the Nudge Browser Extension.

  3. Name your Configuration Profile (i.e. Nudge Configure Brave MacOS).

  4. In the new Configuration Profile, scroll down and select Custom Settings.

  5. Set preference domain to: com.brave.Browser.extensions.diaecjfdpohehjhliaephjnpnlmeajfa

  6. Head to the Nudge Security and grab the deployment policy PLIST file by going to Settings → Browser Extension → Enroll New Users → Managed Deployment → Device Management → select your browser → MacOS. Download the PLIST file in Step 2 of the instructions. In that PLIST, look for the deployment key field and copy.

  7. Replace the string DEPLOYMENT_KEY_HERE with your key copied from Nudge Security earlier. Copy and paste PLIST linked below:

<dict> 	<key>nudge-security-deployment-key</key> 		<string>deployment key here</string> </dict>

Finally, save the policy.

Firefox

  1. Go to Configuration Profiles → New to create a new install policy.

  2. Name your Configuration Profile (i.e. Nudge Install Firefox MacOS).

  3. On the left-nav, scroll down and select Custom Settings.

  4. Click configure and set your preference domain to org.mozilla.firefox

  5. In the text box (or upload field), insert your PLIST code below to install the extension:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "<http://www.apple.com/DTDs/PropertyList-1.0.dtd>"> <plist version="1.0"> <dict>  <key>ExtensionInstallForcelist</key>  <array>   <string>diaecjfdpohehjhliaephjnpnlmeajfa</string>  </array> </dict>

Save the policy.

But wait there's more...

  1. Next, create a new Custom Script to configure the deployment policy for Firefox.

  2. Name your Custom Script (i.e. Nudge Configure Firefox MacOS).

  3. In the new Custom Script, upload the bash script provided by Nudge in the browser extension deployment instructions.

    1. In Nudge, go to Settings → Browser Extension → Enroll new users → Managed Deployment → MacOS → select Firefox → scroll down to step 2 and download the script for Firefox.

  4. Click save.

Verifying installation

Once the extension is installed and configured, you will start to see users showing as Connected in Browser Extension settings page in Nudge. The user discovery process may take up to 72 hours. To manually verify a successful installation and configuration, use the following steps:

Chrome, Edge, and Brave

Verify Extension Installation

Navigate to chrome://extensions in Google Chrome to check if the Nudge Browser extension appears on the list. If the extension is not listed, see the following section for checking the ExtensionInstallForceList.

Verify Extension Deployment Policy Access

Open the extension’s status page by navigating to: chrome-extension://diaecjfdpohehjhliaephjnpnlmeajfa/options.html. Check the deployment status:

  • “Configured” → The extension is fully installed and operational.

  • “Waiting for User” → The extension is still in the user discovery process.

  • “NO_DEPLOYMENT_KEY” → There is an issue with the deployment policy.

Firefox

Verify Extension Installation

Navigate to about:addons in Firefox to check if the Nudge Browser extension appears on the list. If the extension is not listed, see the following section for checking the ExtensionSettings.

Verify Extension Deployment Policy Access

Open the extension’s status page by navigating to: about:addons, find "Nudge Security Browser Extension" and click on "Preferences."

  • “Configured” → The extension is fully installed and operational.

  • “Waiting for User” → The extension is still in the user discovery process.

  • “NO_DEPLOYMENT_KEY” → There is an issue with the deployment policy.

Troubleshooting Jamf

Verify your Mac is MDM-enrolled

Run the following command in your Terminal:

sudo profiles status -type enrollment

You should see something similar to:

Enrolled via MDM: Yes MDM enrollment ID: <UUID>

If you see No, the Mac isn’t actually enrolled with your MDM providers MDM profile. To fix this you’ll need to re-enroll your Mac with your MDM.

Verify your Jamf Configuration Profile was actually delivered to the managed device

In Jamf Pro → Computers → [Select your test Mac] → Management → Configuration Profiles,

check that your Chrome plist profile is listed and status = Installed.

If not installed:

  • Click “View” → see if it’s scoped correctly.

  • Run on the Mac:

sudo jamf recon sudo jamf policy

That will force Jamf to check in and apply configuration profiles.

Validate plist syntax

On your local Mac, before uploading to Jamf run:

plutil -lint com.google.Chrome.plist

You should see the following returned: com.google.Chrome.plist: OK Even a missing semicolon, bad array format, or extra space can break it silently.

Related Articles
Deploy Nudge Browser Extension through Intune
Deploy Nudge Browser Extension through Iru (formerly Kandji)
Did this answer your question?