Closed Bug 1467603 Opened 6 years ago Closed 5 years ago

Provide a way to lock updates on

Categories

(Firefox :: Enterprise Policies, enhancement, P3)

enhancement

Tracking

()

RESOLVED DUPLICATE of bug 1556551
Tracking Status
firefox62 --- affected

People

(Reporter: mkaply, Unassigned)

References

()

Details

We focused on turning off updates.

We should provide a policy to make sure a user can't turn off updates.

See:

https://github.com/mozilla/policy-templates/issues/114
Kirk,

Can you offer your opinion here?

Right now we disable app update using disallowFeature instead of using the prefs.

Obviously the prefs are going away in the future.

Is there something we can do here?

Or will it not matter in the future?
Flags: needinfo?(ksteuber)
I believe that the original reason that I implemented the DisableAppUpdate policy with `disallowFeature` rather than by changing prefs was because I was making separate policies for DisableAppUpdate and DisableSystemAddonUpdate, and locking `app.update.enabled` to `false` would have disabled both of those together. Since then, I have separated those two systems and now they use different prefs (see Bug 1428459), so I don't think there is any need to avoid using prefs to control update at this point.

However, as you rightly point out, the `app.update.enabled` pref will be going away in Bug 1420514. When that happens, the only way to disable updates entirely will be via policy. You may, however, want to make a policy to lock `app.update.auto` to true.
Flags: needinfo?(ksteuber)

We've added a policy for app.update.auto to be locked to true in Firefox 68.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.