How to use policies to enable an extension?

[james633]

I’ve got an extension from a vendor that is closed source so it isn’t eligible for the firefox official distribution and has to be installed by a link to the vendor’s repo at their domain. I’ve pushed it out to clients by GPO with the firefox ADMX.

Since it’s initially untrusted it is disabled by default. I can’t find any references to forcing this to the enabled state. Can that be done with policy?

[mkaply]

We don't currently have a way to enable extensions like this via policy.

An extension being closed source has nothing to do with whether or not an extension can be submitted to AMO. An extension can be unlisted.

[james633]

Ok. Unexpected on the closed source business though because that's what the FF page cites as the reason for it being blocked. It is unlisted as far as I know, their extensions have never been searchable on any of the browser stores. Thanks for the quick response I guess this is something I'm going to need to bring up to the vendor.

https://imgur.com/a/TY8NuVI

DigitalPersona is restricted for violating Mozilla policies
Why did this happen?

This extension, theme, or plugin violates [Mozilla's add-on policies](https://extensionworkshop.com/documentation/publish/add-on-policies/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=blocked-addon).

This add-on violates Mozilla's add-on policies by not providing reviewable source code.
What does this mean?

Until the violation is resolved, this add-on won't be available for download from addons.mozilla.org. If it’s already installed, it will be disabled and users will be informed about the violation. They may choose to enable the add-on again at their own risk.
How does Mozilla enforce its policies?

When Mozilla becomes aware of add-ons, plugins, or other third-party software that seriously compromise Firefox security, stability, or performance and meet [certain criteria](https://extensionworkshop.com/documentation/publish/add-ons-blocking-process/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=blocked-addon), the software may be blocked or restricted from general use. For more information, please read [this support article](https://support.mozilla.org/kb/add-ons-cause-issues-are-on-blocklist).

[mkaply]

So they do have to submit their source to Mozilla for review (to make sure they aren't doing anything bad), but that doesn't make the source open.

I would definitely take it up with them.

[mkaply]

FYI, I talked to our addons folks and after submitting their addon, we asked them questions and they simply never responded.

[james633]

Thanks for looking into that, I’m going to add it to my support case so they can maybe just fix a bureaucracy fail.