Unable to install extension via enterprise policy
Reported by
vedma.vo...@gmail.com,
Nov 14 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Quit Chrome 2. Add an extension to ~/Library/Preferences/com.google.Chrome.plist or /Library/Manage Preferences/@user@/com.google.Chrome.plist, as explained here: http://www.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist. My com.google.Chrome.plist file looks like this: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ExtensionInstallForcelist</key> <array> <string>oiklnmidopglhlhpielmkojkbhaebejm;file://@path@/crx_update_manifest.xml</string> </array> <key>>ExtensionInstallSources</key> <array> <string>file://@path@/*</string> </array> </dict> </plist> 3. Restart your computer 4. Open Chrome What is the expected behavior? 1. chrome://policy should list the policies that are set, including the extension that was added. 2. The extension should be installed. What went wrong? The policy list is loaded correctly in chrome://policy, but the extension is never installed. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.94 (Official Build) Channel: n/a OS Version: 10.10.5 Flash Version: Shockwave Flash 27.0.0.183 I tried to install extension from local file and from local http server, but it did not work. On windows platform it works correctly. Also I saw browser logs and did not catch any errors in this area. Are there any other installation ways via GPO?
,
Nov 14 2017
The spec for ExtensionInstallForcelist and ExtensionInstallSources does not call for "file:" in the <string> entry for Mac. See http://dev.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist and http://dev.chromium.org/administrators/policy-list-3#ExtensionInstallSources. Is that the issue?
,
Nov 15 2017
Didn't have a Mac machine with GPO environment, hence adding "TE-NeedsTriageFromMTV" label for further triage from MTV
,
Nov 15 2017
,
Nov 15 2017
The spec for ExtensionInstallForcelist and ExtensionInstallSources does not call for "file:" in the <string> entry for Mac. Not only for "file". "http" also does not work.
,
Nov 16 2017
+Yining for triaging.
,
Nov 16 2017
,
Nov 20 2017
In a forum post Nov 20 2017, the user acknowledged "file:" should not be in the plist, and acknowledged https was required, but refused to change his code.
,
Nov 20 2017
The user's comment: Why ExtensionInstallForcelist does not contain "file://". It is normal reference. And it is works on Windows platform! "<key>>" is typo. My plist does not contain extra ">". I won't try with https server, because i'm interested in reference "file://"
,
Nov 21 2017
From http://dev.chromium.org/administrators/policy-list-3#ExtensionInstallForcelist. Each list item of the policy is a string that contains an extension ID and an "update" URL separated by a semicolon (;). The extension ID is the 32-letter string found e.g. on chrome://extensions when in developer mode. The "update" URL should point to an Update Manifest XML document as described at https://developer.chrome.com/extensions/autoupdate. I could not see any limitations regarding update url. On page https://developer.chrome.com/extensions/autoupdate I also could not see any limitations. Example described there contain http not https. "update_url": "http://myhost.com/mytestextension/updates.xml" So, I can use any URL (http, https, file) to Install application via GPO. But it does not work on Mac OS Platform. Only on Windows Platform this solution works fine.
,
Nov 21 2017
I don't have a Mac GPO environment either so can't repro this bug. as per c#8, this issue require user to fix it in his end. give to mheinsohn@chromium.org to decide should resolve this bug as Won'tFix.
,
Nov 21 2017
,
Dec 20 2017
Based on #2, #5, #8, and #9, the user knows it's a problem with his code, yet refuses to change his code. Marking WontFix because it's not a Chrome problem. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by manoranj...@chromium.org
, Nov 14 2017Components: Enterprise
Labels: Needs-Triage-M62