Implement "chrome.storage.managed"

VERIFIED FIXED in Firefox 67

Status

defect
P5
normal
VERIFIED FIXED
4 years ago
3 months ago

People

(Reporter: ido.y, Assigned: mkaply)

Tracking

(Blocks 3 bugs, {dev-doc-needed})

45 Branch
mozilla67
Dependency tree / graph

Firefox Tracking Flags

(firefox67 verified, firefox68 verified)

Details

(Whiteboard: [design-decision-approved][triaged])

Attachments

(3 attachments)

Reporter

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36
Reporter

Comment 1

4 years ago
https://developer.chrome.com/extensions/manifest/storage

the managed storage is allow to externally config extension for massive installation (e.g. by using GPO)
in XUL we had the option to do that by using the "nsIWindowsRegKey"
in webExtension that will be the best alternative for doing the configuration
Component: Add-ons Manager → WebExtensions

Comment 2

3 years ago
there's nothing in Fx that enables setting all to same back end configuration - Jeff are there plans?
Flags: needinfo?(jgriffiths)
Priority: -- → P3
Whiteboard: triaged
(In reply to :shell escalante from comment #2)
> there's nothing in Fx that enables setting all to same back end
> configuration - Jeff are there plans?

We have some initial discussions about reforming ESR to be more useful to enterprises. I don't think this feature is on the list yet, and I think I would prefer any Firefox work be driven from Web Extensions requirements. The initial ESR work will almost certainly be mainly installer work.
Flags: needinfo?(jgriffiths)
This is quite required for my cases. For my customer companies I provide some addons for their common requirements, and distribute it with an MCD configuration file to change their behaviors for each customer. For example:
https://addons.mozilla.org/firefox/addon/force-addon-status/
https://addons.mozilla.org/firefox/addon/permissions-auto-registerer/
https://addons.mozilla.org/firefox/addon/ui-text-overrider/
Reporter

Comment 5

3 years ago
is there anything new about this?

Updated

3 years ago
Blocks: 1279446

Updated

3 years ago
Whiteboard: triaged → [design-decision-needed][triaged]
Blocks: 1291627

Updated

3 years ago
Component: WebExtensions: Untriaged → WebExtensions: General

Updated

3 years ago
Priority: P3 → P5
Whiteboard: [design-decision-needed][triaged] → [design-decision-approved][triaged]
Duplicate of this bug: 1337150
Assignee

Comment 8

2 years ago
This would be a blocker for distributions as well. Is there a reason this is still unconfirmed if it has been triaged/approved?
Blocks: 1333828

Comment 9

2 years ago
Because we rarely bother flipping the status from unconfirmed, its always seemed like a pointless make work step in Bugzilla to me. I've flipped it to new :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Duplicate of this bug: 1337150

Comment 11

2 years ago
Mozilla Bug 1215062 decided to disallow to access about:config preferences. So, It is impossible to convert Configuration Mania to a WebExtension. Not only this extensions such as QuickJ , GuI config , TMP
etc cannot be ported as well.

Since these are top extensions and have at some point been featured on mozilla,
Mozilla should probably allow some leeway and implement the necessary apis or face user backlash.

Comment 12

2 years ago
With the conversion of extensions to WebExtensions, we are unable to deploy our settings to various deployed extensions, such as uBlock Origin. If this is not the proper way for an extension to allow settings to be managed by an administrator, then what is?

Updated

2 years ago
See Also: → 1386427
(In reply to Austin from comment #12)
> With the conversion of extensions to WebExtensions, we are unable to deploy
> our settings to various deployed extensions, such as uBlock Origin. If this
> is not the proper way for an extension to allow settings to be managed by an
> administrator, then what is?

As a workaround for enterprise (business) use, I've developed a native messaging host to read configs from MCD configuration files. Until chrome.storage.managed is landed, we need to do something like this by self.

https://github.com/clear-code/mcd-go (library for Golang)
https://github.com/clear-code/ieview-we (example application)
Depends on: 1386427

Comment 14

2 years ago
Please note that bug 1386427 contains a basic implementation of chrome.storage.managed and I've successfully used this to configure extensions. A test of uBlock Origin would be appreciated.
Assignee

Updated

2 years ago
No longer blocks: 1333828

Updated

2 years ago
Component: WebExtensions: General → WebExtensions: Storage

Updated

Last year
Product: Toolkit → WebExtensions
:mkaply - with support for chrome.storage.managed in release 57, and support for Windows GPO in release 60, is this bug still applicable?  Or can it be closed?
Flags: needinfo?(mozilla)
Assignee

Comment 16

Last year
This bug is still applicable. I think we need to add support to GPO for settings chrome.storage.managed values?

I honestly don't know how the mapping works. I'll see if this is something our intern wants to take on.
Flags: needinfo?(mozilla)
Assignee

Comment 17

Last year
Right now the managed storage only looks in Native Manifests:

https://searchfox.org/mozilla-central/source/toolkit/components/extensions/parent/ext-storage.js#29

We would need to add code to support a new type of manifest maybe? And then provide policy code to set it.

Updated

10 months ago
Assignee

Updated

9 months ago
Assignee: nobody → mozilla
Assignee

Comment 19

9 months ago
I'm moving this to I plan to start work on this soon.
Status: NEW → ASSIGNED
Assignee

Updated

4 months ago
Depends on: 1530465
Assignee

Comment 21

4 months ago
Keywords: dev-doc-needed

Comment 22

4 months ago
Pushed by mozilla@kaply.com:
https://hg.mozilla.org/integration/autoland/rev/1a0f3a7891f4
Add support for setting chrome.storage.managed via enterprise policy. r=Felipe,zombie,flod

Comment 23

4 months ago
bugherder
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Assignee

Comment 24

3 months ago

Attached are files for testing this bug.

There is a policies.json that sets the value in policy.

There is a simple extension that can be loaded via about:debugging.

After loading, you can debug the extension and view the console and see that the value you set in policy is displayed in the console.

Comment 25

3 months ago
Posted image Bug1230802.png

This issue is verified as fixed on Firefox 68.0a1(20190319095054) and Firefox 67.0b3(20190318154932) under Win 7 64-bit and Mac OS X 10.14.1.

Please see the attached screenshot.

Updated

3 months ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.