Allow Local File Access For Box Tools via Chrome with Jamf Pro
Allows local network access for file sharing between Chrome and Box Tools.
Create a script to create the plist
- Create a script to create a plist using the LocalNetworkAccessAllowedForUrls key and adding in an array of strings with all the Box Domains.
- Example Bash code format:
- defaults write /PATH/TO/FILE SOME_KEY -string SOME_X_VALUE
- repeat as needed
- End Result:
<?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>LocalNetworkAccessAllowedForUrls</key>
<array>
<string>https://uofi.app.box.com:443</string>
<string>https://*.box.com/*</string>
<string>https://*.app.box.com/*</string>
<string>https://*.box.net/*</string>
<string>https://*.boxcn.net/*</string>
<string>https://*.boxcdn.net/*</string>
<string>https://*.boxenterprise.net/*</string>
<!-- Add any other Box-related domains required for your specific setup -->
</array>
</dict>
</plist>
Create the Configuration Profile in Jamf Pro
- Open Jamf Pro and create a new computer configuration profile.
- Configure the “Application and Custom Settings” payload
- Select “Upload”
- Enter in the “Preference Domain” for Google Chrome
- Upload the newly created plist or copy and paste it into the “Upload File” field
- Save the Configuration Profile
OPTIONAL
- Configure the “Privacy Preferences Policy Control (PPPC)” payload
- Enter the Bundle Identifier for Google Chrome
- To find the bundle IDs and Identifiers for apps do the following:
- Create a script using the codesign argument as such:
- codesign --display --requirements – PATH/TO/APP
- codesign --display --requirements – ‘Applications/Google Chrome.app’
- The identifier is labeled in the result like (identifier “com.google.chrome”
- The requirements will be everything after the designated =>
- In “App or Service” select “Add”
- Select “SystemPolicyAllFiles” and “Allow”
- Set the Scope
- Save the Configuration Profile