Require Extension User Login
This guide explains how administrators can configure the Maro browser extension to require login for all users.
Overview
Setting the extension policy require_login forces end-users to authenticate to the Maro browser extension by adding a banner while they are browsing when users are not logged in. To enable, set the require_login Chrome policy key for the Maro extension.
Policy key: require_login
Values: 1 (Windows registry) / true (macOS managed preferences)
Extension ID: use the browser-specific ID below

Extension IDs
The Maro extension has different IDs on the Chrome Web Store and the Edge Add-ons store. Use the correct ID for your target browser throughout this guide.
Browser | Extension ID | Store Link |
|---|---|---|
Google Chrome | elopbipdaffijbfafcgmkilmmegldlmp | Chrome Web Store |
Microsoft Edge | ccpahlhjnkgadkgicbmdenmgonjjcomc | Edge Add-ons |
Option A: Manual installation (testing / small deployments)
Windows (Chrome)
Save as enable-require-login-chrome-windows.ps1, then run in elevated PowerShell:
Run with:
Windows (Edge)
Use the same script pattern, but with the Edge registry path:
macOS (Chrome / Edge)
The recommended way on macOS is an MDM profile. For testing, you can write the managed preference directly.
Save as enable-require-login-mac.sh, then run with sudo:
Option B: MDM deployment (recommended for production)
Deploy the require_login policy through your MDM platform as a managed browser extension policy.
Jamf Pro (macOS)
- Create a new Configuration Profile in Jamf Pro.
- Add a Custom Settings payload.
- Set the preference domain to your target browser + extension ID:
- Chrome: com.google.Chrome.extensions.elopbipdaffijbfafcgmkilmmegldlmp
- Edge: com.microsoft.Edge.extensions.ccpahlhjnkgadkgicbmdenmgonjjcomc
- Configure the payload to set require_login:
- Scope the profile to your target devices or groups.
- Deploy the configuration profile.
If your organization uses both Chrome and Edge, create a separate configuration profile for each browser using the corresponding preference domain.
Microsoft Intune (Windows)
- Navigate to Devices > Configuration profiles in the Intune admin center.
- Create a new profile (Windows 10 and later, Settings catalog).
- Add the following registry-based setting for your target browser:
Chrome:
- Registry path: SOFTWARE\\\\Policies\\\\Google\\\\Chrome\\\\3rdparty\\\\extensions\\\\elopbipdaffijbfafcgmkilmmegldlmp\\\\policy
- Value name: require_login
- Value type: REG_DWORD
- Value: 1
Edge:
- Registry path: SOFTWARE\\\\Policies\\\\Microsoft\\\\Edge\\\\3rdparty\\\\extensions\\\\ccpahlhjnkgadkgicbmdenmgonjjcomc\\\\policy
- Value name: require_login
- Value type: REG_DWORD
- Value: 1
- Assign the profile to your target device groups.
Restart the browser, or visit chrome://policy or edge://policy and click Reload policies to apply.
Troubleshooting
- Policy not applying: confirm the extension ID matches the installed extension and reload policies (`chrome://policy` / edge://policy).
- macOS profile issues: confirm the preference domain is correct for the browser and that the profile is installed on the device.
- Still seeing unauthenticated access: verify the require_login key is present and set to the expected value, then fully restart the browser.