Configuring AddOn Parameters using `policy.json`?
I'm setting up addon installation through `policy.json`. Below is an example. I am wondering howto configure addons thus installed using the same file. Is it possible? If yes: where to find addon-specific keys/options? As an example: when providing below `policy.json`, starting any fresh firefox profile/installation produces the dialog "Startpage.com - Private Search Engine would like to change your default search engine from Google to Startpage.com - English. Is that OK?", followed by yes/no buttons. I would like to be able to just make the addon do so forgoing the dialog.
Thanks for any pointers.
{
"policies": {
"ExtensionSettings": {
"*": {
"blocked_install_message": "Installation of extensions only allowed from 'policy.json'.",
"installation_mode": "blocked"
},
"{20fc2e06-e3e4-4b2b-812b-ab431220cada}": {
"installation_mode": "force_installed",
"install_url": "https://addons.mozilla.org/firefox/downloads/latest/startpage-private-search/latest.xpi"
}
},
"ExtensionUpdate": true
}
}
Усі відповіді (2)
@Dropa: that's exactly what I started out with, and configuring FF itself, as well as installing the AddOns/extensions is a breeze. What I am struggling with is the configuration of the extensions themselves...
It's up to the extension developer to add support for being managed by policies:
https://extensionworkshop.com/documentation/publish/add-on-policies/
And then you would use 3rdparty to manage them:
https://github.com/mozilla/policy-templates/blob/master/README.md#3rdparty
Specifically with the Startpage extension, though, you can not use policy to allow an extension to change the search engine.
There are policies to manage search engines:
but they only work on the ESR.