Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Deploying Firefox ESR for Mac with policies.json

  • 1 Antwort
  • 1 hat dieses Problem
  • 128 Aufrufe
  • Letzte Antwort von D3xbot

more options

I'm working on building a deployment for Firefox 78.1.0 ESR in a mixed Windows/macOS environment. I've got a policies.json file that works, and was able to install it on Windows via a batch script that runs the installer MSI, creates the distribution directory, and copies the policies.json to that location.

Where I'm struggling is getting this deployed on the Mac side of things. I've followed the directions to apply policy and remove the quarantine here: https://support.mozilla.org/en-US/kb/deploying-firefox-customizations-macos While this works on my Mac, when I deploy it to my test collection (via AirDrop, Self-Service, or by running the PKG file made by JAMF Composer), macOS says the app is damaged and should be deleted.

Does anyone know a way around that?

I'm working on building a deployment for Firefox 78.1.0 ESR in a mixed Windows/macOS environment. I've got a policies.json file that works, and was able to install it on Windows via a batch script that runs the installer MSI, creates the distribution directory, and copies the policies.json to that location. Where I'm struggling is getting this deployed on the Mac side of things. I've followed the directions to apply policy and remove the quarantine here: https://support.mozilla.org/en-US/kb/deploying-firefox-customizations-macos While this works on ''my'' Mac, when I deploy it to my test collection (via AirDrop, Self-Service, or by running the PKG file made by JAMF Composer), macOS says the app is damaged and should be deleted. Does anyone know a way around that?

Ausgewählte Lösung

In speaking with my supervisor, I found that in building a policy, I can instruct JAMF to install Firefox and run a script post-install. This allowed me to customize Firefox without worrying about signing apps or gatekeeper.

Script:

#! /bin/bash

cd /Applications mkdir ./Firefox.app/Contents/Resources/distribution printf "Your minified JSON\n formatted to Firefox's liking with printf" > ./Firefox.app/Contents/Resources/distribution/policies.json xattr -r -d com.apple.quarantine Firefox.app

Mind the whitespace - when I tried to collapse the spaces, Firefox did not like it. For instance: {

 "policies": {
   "Bookmarks": [
    {
     "Placement": "toolbar",
     "Title": "Google",
     "URL": "https://www.google.com"
    }
   ]
 }

} would become {\n "policies": {\n "Bookmarks": [\n {\n "Placement": "toolbar",\n "Title": "Google",\n "URL": "https://www.google.com"\n }\n ]\n }\n}

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (1)

more options

Ausgewählte Lösung

In speaking with my supervisor, I found that in building a policy, I can instruct JAMF to install Firefox and run a script post-install. This allowed me to customize Firefox without worrying about signing apps or gatekeeper.

Script:

#! /bin/bash

cd /Applications mkdir ./Firefox.app/Contents/Resources/distribution printf "Your minified JSON\n formatted to Firefox's liking with printf" > ./Firefox.app/Contents/Resources/distribution/policies.json xattr -r -d com.apple.quarantine Firefox.app

Mind the whitespace - when I tried to collapse the spaces, Firefox did not like it. For instance: {

 "policies": {
   "Bookmarks": [
    {
     "Placement": "toolbar",
     "Title": "Google",
     "URL": "https://www.google.com"
    }
   ]
 }

} would become {\n "policies": {\n "Bookmarks": [\n {\n "Placement": "toolbar",\n "Title": "Google",\n "URL": "https://www.google.com"\n }\n ]\n }\n}