This article includes the process of enforcing the activation of Josys browser extension on any browser (Google Chrome/Microsoft Edge) by creating a configuration profile and adding the managed data using Kandji.
The deployment includes the following two steps:
1. Force Push Chrome Extension
2. Adding Managed Data for the Extension
1. Force Push Chrome Extension
A) Creating a Configuration Profile for the extension
Step 1: Create a "force_install_chrome_extension.mobileconfig" XML file with the following code.
Step 2: In the file, replace the EXTENSION_ID with the Josys browser extension id of your respective browsers.
- Chrome Extension ID:
moaklgcgokbgplldonjkoochhlefkbjf;https://clients2.google.com/service/update2/crx
- Edge Extension ID:
hjifncajikcdkhlofdjjlhcjoennmdfc;https://edge.microsoft.com/extensionwebstorebase/v1/crx
<?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>PayloadContent</key> <array> <dict> <key>PayloadType</key> <string>com.google.Chrome</string> <key>PayloadUUID</key> <string>UUID-FORCE-INSTALL</string> <key>PayloadVersion</key> <integer>1</integer> <key>PayloadDisplayName</key> <string>Chrome Extension Force Install</string> <key>DeveloperToolsAvailability</key> <integer>1</integer> <key>ExtensionInstallForcelist</key> <array> <string>EXTENSION_ID</string> </array> </dict> </array> </dict> </plist>
B) Uploading the Configuration Profile to Kandji
Step 1: Log in to the Kandji Admin Console.
Step 2: Navigate to the Library module. Click Add New and select Custom Profile.
Step 3: Upload the force_install_chrome_extension.mobileconfig file created in Section A.
Step 4: Give a name to the profile, for example, "Chrome Extension Force Install".
Step 5: Assign the file to the relevant Blueprints and device families, and Save the profile.
2. Adding Managed Data for the Extension
A) Creating a Configuration Profile for the Managed Data
Step 1: Create a "managed_data_for_extension.mobileconfig" XML file with the following code.
Step 2: In the file, replace theEXTENSION_ID, KEY, and USER_EMAIL with the Josys browser extension id, organization key, and the user's email respectively.
- Chrome Extension ID:
moaklgcgokbgplldonjkoochhlefkbjf;https://clients2.google.com/service/update2/crx
- Edge Extension ID:
hjifncajikcdkhlofdjjlhcjoennmdfc;https://edge.microsoft.com/extensionwebstorebase/v1/crx
<?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>PayloadContent</key> <array> <dict> <key>PayloadType</key> <string>com.google.Chrome.extensions.EXTENSION_ID</string> <key>PayloadUUID</key> <string>UUID-MANAGED-DATA</string> <key>PayloadVersion</key> <integer>1</integer> <key>PayloadDisplayName</key> <string>Managed Data for Chrome Extension</string> <key>OrganizationKey</key> <string>KEY</string> <key>UserEmail</key> <string>USER_EMAIL</string> </dict> </array> </dict> </plist>
B) Uploading the Managed Data Profile to Kandji
Step 1: Log in to the Kandji Admin Console.
Step 2: Navigate to the Library module. Click Add New and select Custom Profile.
Step 3: Upload the managed_data_for_extension.mobileconfig file created in Section B.
Step 4: Give a name to the profile, for example, "Managed Data Force Install".
Step 5: Assign the file to the relevant Blueprints and device families, and Save the profile.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article