Skip to content

Update macos.md #154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
josh-ricketts-enable wants to merge 1 commit into
base: dev
Choose a base branch
from
+128 −0
Open

Update macos.md #154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
128 changes: 128 additions & 0 deletions docs/deployment/chrome-edge-deployment-instructions/macos.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,133 @@ icon: apple
---

# MacOS
I'd recommend that this be deployed via your MDM if the goal is to auto-deploy it without user interaction.

A custom .mobileconfig file can be uploaded to most MDMs for deployment if they don't have their own Google Chrome, or Microsoft Edge profile building functionality baked-in.

Here's an example profile of the XML to create a mobileconfig that will install this in Microsoft Edge and Google Chrome.

```
<?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>ExtensionInstallForcelist</key>
<array>
<string>benimdeioplgkhanklclahllklceahbe</string>
</array>
<key>PayloadDisplayName</key>
<string>Google Chrome</string>
<key>PayloadIdentifier</key>
<string>com.google.Chrome.23E5DDCF-1EB2-4869-9510-5E47D6640A85</string>
<key>PayloadType</key>
<string>com.google.Chrome</string>
<key>PayloadUUID</key>
<string>23E5DDCF-1EB2-4869-9510-5E47D6640A85</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
<dict>
<key>ExtensionInstallForcelist</key>
<array>
<string>knepjpocdagponkonnbggpcnhnaikajg</string>
</array>
<key>PayloadDisplayName</key>
<string>Microsoft Edge</string>
<key>PayloadIdentifier</key>
<string>com.microsoft.Edge.DD4A940A-B216-4D5E-8B2C-1EF2CAFF7F38</string>
<key>PayloadType</key>
<string>com.microsoft.Edge</string>
<key>PayloadUUID</key>
<string>DD4A940A-B216-4D5E-8B2C-1EF2CAFF7F38</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</array>
<key>PayloadDescription</key>
<string>This profile installs and enforces the 'Check' browser extension from CyberDrain on Google Chrome and Microsoft Edge web browsers. </string>
<key>PayloadDisplayName</key>
<string>Check CyberDrain</string>
<key>PayloadIdentifier</key>
<string>020D4Z7P-7F1A-4723-89CB-1826F8BAF4B5</string>
<key>PayloadOrganization</key>
<string>YOUR ORG NAME</string>
<key>PayloadScope</key>
<string>System</string>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>020D4Z7P-7F1A-4723-89CB-1826F8BAF4B5</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>RemovalDate</key>
<date>2044-05-19T21:46:44Z</date>
<key>TargetDeviceType</key>
<integer>5</integer>
</dict>
</plist>
```
You could also deploy it in Chrome via command-line by creating the proper JSON object in the correct directory in the core /Library directory in macOS. Credit to @cezaraugusto for the script (slightly modified to simply install 'Check' if no parameter is passed...though technically you could pass any other Chrome extension ID after the script path and it would install that extension).

```
#!/bin/bash

# https://developer.chrome.com/docs/extensions/mv3/external_extensions/#preferences
# Credit to #cezaraugusto# from GithubGist for this script...slightly modified for the purposes of installing Check by Cyberdrain if no parameter is passed
# https://gist.github.com/cezaraugusto
# https://gist.github.com/cezaraugusto/0101d2cb251c088f398ca0f8d4495ca0

extension=$1

if [[ -z "$extension" ]]; then
extension="benimdeioplgkhanklclahllklceahbe"
fi
install_chrome_extension() {
chrome_extensions_folder="/Library/Application Support/Google/Chrome/External Extensions"
chrome_extensions_preferences_file="$chrome_extensions_folder/$extension.json"
# This URL is used by Chrome to check for updates to external extensions
update_services_url="https://clients2.google.com/service/update2/crx"

if [[ -d "$chrome_extensions_folder" ]]; then
mkdir -p "$chrome_extensions_folder"
fi

echo "{" > "$chrome_extensions_preferences_file"
echo " \"external_update_url\": \"$update_services_url\"" >> "$chrome_extensions_preferences_file"
echo "}" >> "$chrome_extensions_preferences_file"

echo "Added \"$chrome_extensions_preferences_file\""
}

if [ $# -ne 1 ]; then
echo "Usage: $0 <extension_id>"
exit 1
fi

install_chrome_extension "$extension"

# Usage:
# ./install_extension.sh <extension_id>
# Sample: adding React Dev Tools from command-line to Chrome
# ./install_extension.sh fmkadmapgofadopljbjfkapdkoienihi
```

This would not install the extension until the next time Chrome is launched, and then it will require the user to approve it.

<img width="448" height="330" alt="SCR-20260520-krbi" src="https://github.com/user-attachments/assets/f53a13fe-c16b-4941-aa39-0799b2b32b6e" />



Due to limitations like this it really would be better to push it via an MDM.


### I don't know if this is the kind of feedback, or instruction you're looking for with macOS. If it IS, and you just need more screenshots, better examples, and more official language I'd be happy to assist with that.




### Original message below
Coming soon. If you have experience deploying managed MacOS browser extensions, please contribute to the [docs via GitHub](https://github.com/CyberDrain/Check/tree/dev/docs). All Mac resources in the GitHub repo should be considered inaccurate until tested.&#x20;