Closed Bug 1436840 Opened 8 years ago Closed 8 years ago

Policy engine - Add support for enterprise-only policies

Categories

(Firefox :: Enterprise Policies, enhancement)

Product:
Firefox
Component:
Enterprise Policies
Version:
60 Branch
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Firefox 60
Tracking Flags:
Tracking Status
firefox60 --- fixed

People

(Reporter: Felipe, Assigned: Felipe)

References

Details

Attachments

(1 file)

Bug 1436840 - Policy engine: Add support for enterprise-only policies.
59 bytes, text/x-review-board-request
mkaply
: review+
Details
We should support a parameter specified in the schema that, when specified, will only allow that policy to be activated on ESR builds.
Examples of these policies: Anything search engine related. Anything that changes the homepage. Kev: Any other policies that we should not allow on release?
Flags: needinfo?(kev)
What we're trying to figure out here is if there are some policies that should be enterprise only (as in only available in ESR). I understand the though that maybe this whole system should be ESR/enterprise only. We're open to that The problem is that we know there are enterprises that want to continue to use the regular release cycle. We have to figure out how to solve for that. On Windows, solution could be "only if connected to AD" What I'm looking for right now is what are the policies that would be most likely used for hijacking.
I suggested in bug 1429150 that the policy to disable app updates should also be ESR only
With this patch, it is just a matter of annotating the policy with `"enterprise_only": true` in the schema. Local builds and try builds will still allow every policy to run, to make it easier to test/develop. Official builds will require the release channel to be esr to allow the policy.
gah, forgot to `hg add` the test, as I always do..
(In reply to Mike Kaply [:mkaply] from comment #2) > What we're trying to figure out here is if there are some policies that > should be enterprise only (as in only available in ESR). > > I understand the though that maybe this whole system should be > ESR/enterprise only. We're open to that > > The problem is that we know there are enterprises that want to continue to > use the regular release cycle. We have to figure out how to solve for that. > > On Windows, solution could be "only if connected to AD" > > What I'm looking for right now is what are the policies that would be most > likely used for hijacking. I'm on the "machine must be authenticated to an AD" on Windows clients for the policy engine to be used for anything on release were it to be available there. Otherwise I'd support an ESR-only (or whatever we end up calling the version of Firefox that supports managed desktops/environments) approach. Policies I'd be most concerned about would be updates of any kind (updates, blocklist, add-ons updates, etc.), sideload scopes, search, newtab, home page, and proxy settings. Explicitly supporting those types of policies on release is something I'd like to see us avoid.
Flags: needinfo?(kev)
Comment on attachment 8949563 [details] Bug 1436840 - Policy engine: Add support for enterprise-only policies. https://reviewboard.mozilla.org/r/218920/#review231128
Attachment #8949563 - Flags: review?(mozilla) → review+
Pushed by felipc@gmail.com: https://hg.mozilla.org/integration/autoland/rev/28a1060ab283 Policy engine: Add support for enterprise-only policies. r=mkaply
https://hg.mozilla.org/mozilla-central/rev/28a1060ab283
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox60: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 60
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: