Chromium Browsers in Mac

Overview

This document outlines the steps to deploy the Swift Security Chrome browser extension on Mac devices using Kanji.

Extension Details

• Extension ID: caagpeigabceamfbclichjenfkcnekha

• Installation URL: https://clients2.google.com/service/update2/crx

Deployment Steps

Step 1: Create a Classic Blueprint

1. Navigate to the Blueprint Section:

   • Click on Blueprint in the left-side pane.

   • Click on New Blueprint at the top-right corner.

   • Select New Classic Blueprint and create the blueprint from scratch.

Step 2: Enroll Devices

1. Add Devices to the Blueprint:

   • Once the blueprint is created, go to the Enrollment section.

   • Choose Manual Enrollment.

   • Provide the following enrollment link to the client/user:

   • Share the Enrollment Code with the client to complete the device registration process.

Step 3: Create a Custom Profile for Chrome Extension Deployment

1. Go to the Library Section:

   • After enrolling the device, go to the Library section in Kanji.

   • Click on Add New and select Custom Profile.

   • Name the profile (e.g., "Chrome Extension Deployment").

   • Select the Blueprint you created earlier.

2. Upload the .mobileconfig File:

   • Upload the following .mobileconfig file to deploy the Chrome 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>PayloadContent</key>
    <array>
        <dict>
            <key>PayloadType</key>
            <string>com.google.Chrome</string>
            <key>PayloadVersion</key>
            <integer>1</integer>
            <key>PayloadIdentifier</key>
            <string>com.google.Chrome.extension</string>
            <key>PayloadUUID</key>
            <string>ABCDE123-4567-89AB-CDEF-0123456789AB</string> <!-- Nested unique UUID -->
            <key>PayloadDisplayName</key>
            <string>Chrome Extension Deployment</string>
            <key>PayloadDescription</key>
            <string>Forces the installation of a specified Chrome extension.</string>
            <key>PayloadEnabled</key>
            <true/>
            <key>ExtensionInstallForcelist</key>
            <array>
                <string>caagpeigabceamfbclichjenfkcnekha;https://clients2.google.com/service/update2/crx</string>
            </array>
        </dict>
    </array>
    <key>PayloadDescription</key>
    <string>Configuration profile to deploy Chrome extension.</string>
    <key>PayloadDisplayName</key>
    <string>Chrome Extension Deployment Profile</string>
    <key>PayloadIdentifier</key>
    <string>com.yourorganization.ChromeExtensionDeployment</string>
    <key>PayloadOrganization</key>
    <string>Your Organization</string>
    <key>PayloadScope</key>
    <string>System</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>33D3F08D-FCB8-4D42-9744-E103FC60E05E</string> <!-- Top-level unique UUID -->
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>

1. Save the Profile:

   • After uploading the .mobileconfig file, click on Save to save the custom profile.

Step 4: Monitor Deployment Activity

1. Monitor the Activity:

   • Once the profile is added to the blueprint and devices are enrolled, you can monitor the deployment activity on the devices to ensure the extension is properly installed.