Deploy policies.json for Firefox

Erm why would we want to block addons?

We wouldn’t, but the other options are useful such as default homepages, bookmarks, etc

This is what I have so far, Will test it out on the Freeside machines next time I’m in!

{
  "policies": {
    "BlockAboutAddons": false,
    "BlockAboutConfig": false,
    "BlockAboutSupport": false,
    "BlockAboutSupport": false,
    "CreateMasterPassword": false,
    "DisableAppUpdate": false,
    "DisableBuiltinPDFViewer": false,
    "DisableDeveloperTools": false,
    "DisableFeedbackCommands": false,
    "DisableFirefoxScreenshots": false,
    "DisableFirefoxAccounts": false,
    "DisableFirefoxStudies": true,
    "DisableFormHistory": false,
    "DisablePocket": false,
    "DisablePrivateBrowsing": false,
    "DisableSysAddonUpdate": true,
    "DisplayBookmarksToolbar": false,
    "DisplayMenuBar": false,
    "DontCheckDefaultBrowser": true,
    "RememberPasswords": true,
    "Homepage": {
      "URL": "https://forums.freeside.co.uk",
      "Locked": false
    },
    "FlashPlugin": {
      "Allow": ["https://vcenter.net.dcs.hull.ac.uk"]
    },
  "Bookmarks": [
    {"Title": "Freeside Blog",
     "URL": "http://freeside.co.uk",
     "Placement": "toolbar",
     "Folder": "Bookmarks"
     },
    {"Title": "Freeside Forum",
     "URL": "http://forums.freeside.co.uk",
     "Placement": "toolbar",
     "Folder": "Bookmarks"
     }
    ]
  }
}

This works in Firefox 60 but currently atm satable is on version 58. I’ve made a autoconfig.json which will work for now just need to write the fab code to deploy it.

Turns out the distribution.ini file does everything we need.

1 Like