Thank you Jim, Kris and Alexandre,
@Alexandre, thank you for the link to your python module however in our windows
environment I would like to stick to already available tools and avoid having
to install and maintain the python binaries on all 800 workstations.
@kris and Jim, between your replies I believe I have a solution. Based on Mike
Kaply's blog, if I set pref("extensions.autoDisableScopes", 11); in the
autoconfig file (which we already leverage) it will allow the enabling to
extensions dropped into installation directory as I have done in testing. This
should only auto enable extensions in the installation directory and not affect
user installed extensions, now allow unprivileged malware to auto install
extensions. Also of note, I changed the setting from defaultpref to pref
because this will be deployed to existing users and it is my understanding that
defaultpref is only effective for completely new FF profiles.
@Jim, what I don't understand is the need for extensions.enabledScopes. With
the default settings I am already able to get FF to install extensions in the
installation directory.
Best Regards,
- Brian
> On Jul 3, 2017, at 6:56 AM, Jim Mathies <[email protected]> wrote:
>
> I know this works on Windows, I have yet to test it on Mac. FYI we're
> working on an MDN document for this currently.
>
> --
>
> Install Steps:
>
> 1) Find the Firefox installation on the local system (May be multiple
> installs)
> 2) Open all the files under
>
> (Firefox install)\defaults\pref
>
> and search for a single text line entry in each that starts with:
>
> pref('general.config.filename'
>
> if the text line is found, parse the string to identify the currently in use
> Auto Config file name -
>
> pref('general.config.filename', 'firefox.cfg');
>
> Note, this line may not match exactly. Keying off of
> 'general.config.filename' might be best since variations may exist (single
> vs. double quotes, whitespace, etc.). The goal here is to identify if an
> auto configuration file has already been installed. This is something
> enterprise admins may wish to add.
>
> 3) If no Auto Config setting was found, create a new js file (any name will
> do.. forcepoint.js would work) in the 'pref' directory and add the following
> text to it:
>
> pref('general.config.filename', 'firefox.cfg'); // any name will do, but
> only one file can be defined
> pref('general.config.obscure_value', 0);
>
> This configuration defines an auto configuration file we can use to define
> custom settings controlling web extensions installation.
>
> 4) Add the Auto Config file to the binary folder of Firefox as specified in
> the 'general.config.filename' setting:
>
> (Firefox install)\firefox.cfg
>
> 5) Open the Auto Config file and append the following text:
>
> // empty comment up top - must be here
> defaultPref("extensions.autoDisableScopes", 0);
> defaultPref("extensions.enabledScopes", 15);
>
> This change will allow the loading of add-ons without prompting the user.
>
> 8) Install the signed WebExtension to a location on the system and register
> it using platform specific methods.
>
> 9) Launch Firefox, the WebExtension should be running.
>
>
> -----Original Message-----
> From: Enterprise [mailto:[email protected]] On Behalf Of Brian
> Thomas
> Sent: Friday, June 30, 2017 9:26 AM
> To: [email protected]
> Subject: [Mozilla Enterprise] Administratively Install and Enable Extensions
>
> Is it possible to administratively install and enable extensions
> (specifically webex and uBlock Origin) for Firefox ESR 52.2?
>
> I have determined that I can get the plugin to install for all users by
> dropping the XPI file of the extension in "C:\Program Files (x86)\Mozilla
> Firefox\browser\extensions" however the extension will be disabled until the
> end user manually enables it. Furthermore, if the user attempts to install
> the same plugin for their user profile, installation will silently fail
> because and the plugin will remain disabled.
>
> In our environment we control Firefox updates so updating autoconfig.cfg
> isn't an issue.
>
> Thank you in advance for any guidance.
>
> - Brian Thomas
>
> _______________________________________________
> Enterprise mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/enterprise
>
> To unsubscribe from this list, please visit
> https://mail.mozilla.org/listinfo/enterprise or send an email to
> [email protected] with a subject of "unsubscribe"
>
> _______________________________________________
> Enterprise mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/enterprise
>
> To unsubscribe from this list, please visit
> https://mail.mozilla.org/listinfo/enterprise or send an email to
> [email protected] with a subject of "unsubscribe"
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
[email protected] with a subject of "unsubscribe"
