Closed Bug 1512532 Opened 7 years ago Closed 4 years ago

Extension simultaneously installed and locked is installed as disabled

Categories

(Firefox :: Enterprise Policies, defect, P1)

Product:
Firefox
Component:
Enterprise Policies
Version:
65 Branch
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: sasadipo, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce: Install Firefox 64 (non-ESR) and get the policy templates from https://github.com/mozilla/policy-templates Add the policy templates to local machine under C:\Windows\PolicyDefinitions\en-US Run "gpedit.msc" and add the extension information below: Under "Extensions to Install" add the file path to extension (e.g. "C:\win_ff_ext.xpi") Under "Prevent extensions from being disabled or removed" add the extension id (e.g. addon_id@mozilla.org) launch cmd.exe as administrator and update/re-deploy the local policy by running "gpupdate /force" Launch Firefox and go to the "about:addons" page Actual results: Extension is disabled by default, but if user clicks "Enable" in about:addons the extension will be force-installed correctly Expected results: the extension should have been force installed correctly without user having to go to about:addons and enable it manually
Component: Untriaged → Enterprise Policies
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P1
Summary: Enterprise Policies: Firefox extension is shown disabled when "Locked" through GPO → Extension simultaneously installed and locked is installed as disabled

Is this still a problem? I just re-tested it with Firefox Nightly 67, and the bug didn't happen. I wonder if it's just intermittent or if it got fixed by some other change

Flags: needinfo?(sasadipo)

yes, this issue happens intermittently
we are able to reproduce the issue on Firefox 65.0.2 consistently, but I haven't seen the issue with the nightly build (need more testing to verify).

We are able to fix the issue by going into about::debugging and loading the Extension manually

Flags: needinfo?(sasadipo)

I added code for ESR only that always enables the extension after install. This should be fixed in the next ESR in a couple weeks.

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE

@mkaply this bug was reported for non-ESR version of Firefox (see description).
Was the same code added for non-ESR version? If not, please reopen the issue.

(In reply to Shania Asadipour from comment #4)

@mkaply this bug was reported for non-ESR version of Firefox (see
description).
Was the same code added for non-ESR version? If not, please reopen the issue.

There was a change added to nightly that fixes this problem in a different way, which is why you aren't seeing on nightly.

This was reported on 64. Are you seeing in 65?

yes, the issue was reported initially on 64, it also exists on 65.0.2 (see my earlier comment).

yes, the issue was reported initially on 64, it also exists on 65.0.2 (see my earlier comment).

Sorry, I read that comment wrong. Can you try the Firefox beta (66)? I will try there as well.

Can we please know the root cause of the issue? This will help us verify 66 beta as well.

Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---

Can we please know the root cause of the issue? This will help us verify 66 beta as well.

There wasn't really a root cause. Changes were made to WebExtensions to reenable extensions when they are reinstalled and this solved the problem for policies as well.

For the ESR, we added a custom fix for this particular problem (to enable the addon after install).

If 66 needs that fix, we'll add it there, but I don't believe it did in my testing.

I was able to reproduce this issue with firefox 66 beta using the steps in the description.

Version: 64 Branch → 65 Branch

This should be fixed in Firefox 67 which was released today.

please leave this bug open until we can confirm the issue is resolved.

Were you able to confirm this was fixed?

we have not seen this issue with Firefox 67 - I think its safe to close now.

Thank you Mike!

Status: REOPENED → RESOLVED
Closed: 7 years ago → 7 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Still exists in Firefox 68 ESR and Quantum

Flags: needinfo?(mozilla)

Is it intermittent like you said? No one else has reported this issue.

Is the extension only installed via the policy or is it installed somewhere else as well?

Flags: needinfo?(mozilla)

(In reply to Mike Kaply [:mkaply] from comment #16)

Is it intermittent like you said? No one else has reported this issue.

Is the extension only installed via the policy or is it installed somewhere else as well?
Are you asking if we have more than one of the same extension installed?
AFAIK we only have one extension installed through the policy

The extension is installed through the policy only (based on registry key)
Once you click "enable", the extension is force installed properly

I am unable to recreate this problem and I've tried multiple ways. Does it happen with all extensions or a specific one?

(In reply to Mike Kaply [:mkaply] from comment #19)

I am unable to recreate this problem and I've tried multiple ways. Does it happen with all extensions or a specific one?

This happens with one extension - did you need a copy of the extension in order to continue troubleshooting the issue on your end?
Are there logs or something else you can use to investigate the issue?

Flags: needinfo?(mozilla)

This happens with one extension -

Does this extension happen to be installed with some third party application as well as with policy?

Flags: needinfo?(mozilla)

yes, the extension is bundled in our installation package.
Is there any logs or anything we can provide on our end to reach a resolution?

Issue was found in Firefox 69 ESR as well.

We have gone back and forth, and I don't feel like I understand the core problem.

The only reason an extension is installed disabled by default is if it is a third party extension installed via the registry or some global location.

Extensions installed via group policy or policies.json are installed like normal extensions, so they are enabled.

What exactly is the one extension that is causing the problem?

From my understanding, more than one developer is seeing this issue, given the reports in github as well.
The behavior is inconsistent - regardless of which method is being used, the behavior should be consistent each time.
Our extension installation process is documented in the description of the ticket.

I haven't seen any other reports. Is this an internal or external extension? Is it signed?

Yes it is signed.

hey Mike
i am Owen, worked together with Sean A, i was wondering if there any updates or suggestions?

Fresh Install of FF74 and restarting our endpoint services will cause extension to disappear

See:

https://blog.mozilla.org/addons/2020/03/10/support-for-extension-sideloading-has-ended/

We are no longer supporting the mechanism you are using for installing your extension.

Although it should not have disappeared, but the user now has the option to remove it.

If you want to force install an extension, you should be using policy, not this mechanism.

Status: REOPENED → RESOLVED
Closed: 7 years ago → 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.