Extensions Management .json is not working
Hello,
I am trying to create a management policy for extensions where all themes are allowed, some extensions are force installed, other specified ones are allowed, and anything else is blocked. I have been scouring the web looking for samples and I just can't get it to work as intended. Here is a sample of what I have written.
{ "*": { "blocked_install_message": "IT has blocked the installation of UNAPPROVED add-ons. Please contact the IT Service Desk to request approval.", "install_sources": "https://addons.mozilla.org/*", "allowed_types": ["theme","extension"] }, "plugin@okta.com": { "installation_mode": "force_installed", "install_url": "https://addons.mozilla.org/firefox/downloads/file/3601147/okta_browser_plugin.xpi" }, "support@lastpass.com": { "installation_mode": "force_installed", "install_url": "https://addons.mozilla.org/firefox/downloads/latest/lastpass-password-manager/latest.xpi" }, "developer@zoom.us": { "installation_mode": "allowed", "install_url": "https://addons.mozilla.org/firefox/downloads/file/4212428/zoom_new_scheduler-2.1.52.xpi" }, "info@katalon.com": { "installation_mode": "allowed", "install_url": "https://addons.mozilla.org/firefox/downloads/file/3826743/katalon_automation_record-5.5.3.xpi" } }
In this current state, I am allowed to install themes, I get the forced installs, but I can install ANY extension. I don't want that.
If I modify the blocking section with [ "installation_mode": "blocked", ], then I only get the force installed plugins and I can't do anything else. It even removes any previously installed themes or plugins not explicitly forced in. The allowed plugins can't be installed either.
I have also tried it without the "extensions" allowed_type but the result did not change. To recap, I need to block any extensions not explicitly pushed or allowed. Would anyone be able to assist and point out what I may be missing please?
~Regards
الحل المُختار
I redact this question/issue. I found an obscure post that led to my resolution. My issue was that I had the ID's for the "allowed" extensions wrong. I did not realize they were specific as I though only the install URL was needed and that we could name it whatever.
regards.
Read this answer in context 👍 0All Replies (1)
الحل المُختار
I redact this question/issue. I found an obscure post that led to my resolution. My issue was that I had the ID's for the "allowed" extensions wrong. I did not realize they were specific as I though only the install URL was needed and that we could name it whatever.
regards.
Modified