We’ve developed an extension for Firefox which end-users can configure for their purposes automatically by simply visiting a specific page out on the web. This configuration is specific to each application an organization/tenant wishes to use with the extension. For standard users, this should suffice, due to minimal user intervention.
However, now that we’re targeting enterprise organizations who would need to push the extension to their end-users without user intervention, a question’s cropped up about how to pre-configure the extension for each tenant.
I see from the article mentioned below that we might have to go the unlisted/side-loading approach, since the extension will be either downloaded from the AMO or unpacked and tweaked by a customer’s IT department for deployment via GPO/AD.
From Signing and distribution overview | Firefox Extension Workshop
Unlisted add-ons
After accepting the Developer Agreement, you’ll be asked if you want to list your add-on on AMO. Make sure you choose not to list it.
You’ll then be asked if you want your add-on to be side-loaded or not. Side-loading is when your add-on XPI isn’t installed directly by users but instead it is bundled in an application installer.
Question: The extension supports reading configuration from an included JS file. Is it acceptable for the extension to be unpacked after approval/signing and a single JS file be tweaked to include some tenant-specific info? Will this still allow for a “silent” installation with no user intervention?
Thanks!