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 $extension id = "elopbipdaffijbfafcgmkilmmegldlmp" $registrypath = "hklm \\\software\\\policies\\\google\\\chrome\\\3rdparty\\\extensions\\\\$extension id\\\policy" if ( not (test path $registrypath)) { &#x9;new item path $registrypath force | out null } new itemproperty path $registrypath name "require login" value 1 propertytype dword force | out null write host "set require login=1 for extension $extension id" write host "restart chrome (or visit chrome //policy and click 'reload policies') to apply " run with start process powershell verb runas argumentlist ' executionpolicy','bypass',' file','"c \\\path\\\to\\\enable require login chrome windows ps1"' windows (edge) use the same script pattern, but with the edge registry path $extension id = "ccpahlhjnkgadkgicbmdenmgonjjcomc" $registrypath = "hklm \\\software\\\policies\\\microsoft\\\edge\\\3rdparty\\\extensions\\\\$extension id\\\policy" 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 \#!/bin/bash set e extension id chrome="elopbipdaffijbfafcgmkilmmegldlmp" extension id edge="ccpahlhjnkgadkgicbmdenmgonjjcomc" \# chrome domain defaults write "/library/managed preferences/com google chrome extensions ${extension id chrome}" require login bool true \# edge domain (uncomment if using edge) \# defaults write "/library/managed preferences/com microsoft edge extensions ${extension id edge}" require login bool true \# flush the preferences cache so the browser can pick up changes killall cfprefsd 2>/dev/null || true echo "set require login=true for chrome extension ${extension id chrome}" echo "restart the browser (or visit chrome //policy / edge //policy and click 'reload policies') to apply " 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 \<dict> &#x9;\<key>require login\</key> &#x9;\<true/> \</dict> 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