Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Preinstalled Extension in FF 68.1.0esr doesn't work

  • 2 antwurd
  • 1 hat dit probleem
  • 36 werjeftes
  • Lêste antwurd fan letymar2710

letymar2710
letymar2710
more options

Hi, I am preparing a firefox enterprise installation on windows server 2019 with a special configuration and a preinstalled extension. This is a single installation that will be used by all users accessing the server.

Here are the steps I followed:

  1. I installed firefox: Firefox_setup_68.1.0-esr.msi
  2. I transferred our policies.json file to C:\Program Files\Mozilla Firefox\distribution
  3. I transferred our autoconfig.js file to C:\Program Files\Mozilla Firefox\browser\defaults\preferences
  4. I transferred ourextName@ourdomain.local.xpi file to C:\Program Files\Mozilla Firefox\browser\extensions.

By running FireFox, I can see that both the policies and the configurations have been correctly considered, while the extension does not work.

After doing various tests I can say that:

  • the extension is correctly loaded and enabled, in autoconfig.json there are these directive: 
   pref("extensions.autoDisableScopes", 0);
   pref("extensions.enabledScopes", 15);
  • the extension is not signed, but in the autoconfig.json file there is the directive: 
   pref ("xpinstall.signatures.required", false);
  • trying to install the extension from the Add-ons Manager using the item: Install Add-on from file ... It works correctly. Unfortunately I can't use this option, because Extension is installed only for current user.

So, given that the extension works, what's wrong with the preparation procedure, is the directory wrong or some configuration are missing?

Do preinstalled extensions need additional files or a different layout?

I also tried without our policies.json file and leaving only the directive that allows xpi file without signature in the autoconfig.json file and autoDisableScopes/enableScopes.

Any help will be greatly appreciated, thanks

Hi, I am preparing a firefox enterprise installation on windows server 2019 with a special configuration and a preinstalled extension. This is a single installation that will be used by all users accessing the server. Here are the steps I followed: # I installed firefox: '''Firefox_setup_68.1.0-esr.msi''' # I transferred our <code>policies.json</code> file to <code>C:\Program Files\Mozilla Firefox\distribution</code> # I transferred our <code>autoconfig.js</code> file to <code>C:\Program Files\Mozilla Firefox\browser\defaults\preferences</code> # I transferred our<code>extName@ourdomain.local.xpi</code> file to <code>C:\Program Files\Mozilla Firefox\browser\extensions</code>. By running FireFox, I can see that both the policies and the configurations have been correctly considered, while the extension does not work. After doing various tests I can say that: * the extension is correctly loaded and enabled, in <code>autoconfig.json</code> there are these directive: pref("extensions.autoDisableScopes", 0); pref("extensions.enabledScopes", 15); * the extension is not signed, but in the <code>autoconfig.json</code> file there is the directive: pref ("xpinstall.signatures.required", false); * trying to install the extension from the Add-ons Manager using the item: '''Install Add-on from file ...''' It works correctly. Unfortunately I can't use this option, because Extension is installed only for current user. So, given that the extension works, what's wrong with the preparation procedure, is the directory wrong or some configuration are missing? Do preinstalled extensions need additional files or a different layout? I also tried without our <code>policies.json</code> file and leaving only the directive that allows xpi file without signature in the <code>autoconfig.json</code> file and autoDisableScopes/enableScopes. Any help will be greatly appreciated, thanks

Bewurke troch letymar2710 op

Keazen oplossing

Are you sure that the filename is correct if you check the manifest.json file (id.xpi)?

What ID do you get if you install the extension manually ?

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Keazen oplossing

Are you sure that the filename is correct if you check the manifest.json file (id.xpi)?

What ID do you get if you install the extension manually ?

letymar2710
letymar2710 Fraacheigener
more options

thank you very much! I found a syntax error in the url indicated in the property 

    "Extensions": {
         "Install": ["https://addons.mozilla.org/firefox/downloads/somefile.xpi", "//path/to/xpi"],
         "Uninstall": ["bad_addon_id@mozilla.org"],
         "Locked":  ["addon_id@mozilla.org"]
       }

it was not very clear to me what was //path/to/xpi and at the end I saw that using a file url works (like: file:///C:/Program Files/Mozilla Firefox/browser/extensions/extName@ourdomain.local.xpi).

Rereading the indicated page, I also noticed that the ExtensionSettings section was missing, fixing the path and adding this section now the extension is correctly installed and works! Really big thanks!!

Bewurke troch letymar2710 op