Skip to main content

Deploy Nudge Browser Extension through Iru (formerly Kandji)

A guide for Iru 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 a force install list. Be sure to use the same force install list for each browser to prevent policy conflicts during deployment.

  1. Head to your existing force-install lists for Chromium-based browsers and Firefox browsers.

  2. 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

  3. 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

  4. Confirm your changes.

  5. Download the Deployment Policy PLIST from Nudge to extract the deployment key.

    1. In Nudge, go to Settings → Browser Extension → Enroll new users → Managed Deployment → Step 2.

    2. Download the PLIST that contains your organization’s deployment key.

    3. Copy the deployment key in the file and keep handy for the next step. The deployment key is unique to your organization and is used to authenticate the extension.

  6. Replace the DEPLOYMENT_KEY_HERE field in the .mobileconfig file below with your unique deployment key.

    NudgeExtensionConfigureAllBrowsers.mobileconfig

  7. Upload as a Second Custom Profile in Iru:

    1. Library → Add New → Custom Profile → Upload .mobileconfig.

    2. Assign to the same Assignment Map(s).

    3. Save.

New deployments

Follow these instructions if you’re using Iru to force-install an extension for the first time. Iru supports deploying the extension to multiple browsers at a time. Therefore the instructions below apply to all browser types supported by Nudge Security: Chrome, Edge, Firefox, Brave, Comet, Dia, and Atlas.

  1. Create a new configuration profile for the Nudge Browser Extension by going to Library → Add New → Custom Profile → Upload .mobileconfig.

    1. Upload the .mobileconfig file below:

      NudgeExtensionInstallAllBrowsers.mobileconfig

    2. Assign to the same Assignment Map(s).

    3. Save.

  2. Download the Deployment Policy PLIST from Nudge to extract the deployment key.

    1. In Nudge, go to Settings → Browser Extension → Enroll new users → Managed Deployment → Step 2.

    2. Download the PLIST that contains your organization’s deployment key.

    3. Copy the deployment key in the file and keep handy for the next step. The deployment key is unique to your organization and is used to authenticate the extension.

  3. Replace the DEPLOYMENT_KEY_HERE field in the .mobileconfig file below with your unique deployment key.

    NudgeExtensionConfigureAllBrowsers.mobileconfig

  4. Upload as a Second Custom Profile in Iru:

    1. Library → Add New → Custom Profile → Upload .mobileconfig.

    2. Assign to the same Assignment Map(s).

    3. 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

Policy Conflicts

Consolidate all managed extension IDs for a given browser into a single Custom Profile. Duplicate preference domains can override or block enforcement.

Extension Not Appearing

Restart the browser or the device, then manually re-sync from Iru.

Deployment Key Missing

Verify that both installation and deployment profiles are assigned to the same Blueprint.

Preference Domain Errors

Ensure that each Custom Profile uses the correct preference domain listed above.

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.

Validate plist syntax

On your local Mac, before uploading to your MDM 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 the Nudge Security Browser Extension to MacOS through Jamf
Did this answer your question?