Issue metadata
Sign in to add a comment
|
Enterprise policy force install removes "Allow access to file URLs" option
Reported by
k.marsh...@texthelp.com,
Sep 26 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version : Version 61.0.3163.100 (Official Build) (64-bit) What steps will reproduce the problem? (1) Force install a chrome extension from enterprise policy. (2) the extension no longer has the "Allow access to file URLs" What is the expected result? I expect to see the "Allow access to file URLs" in chrome://extensions/ for this extension when force installed What happens instead? I only see the option "Allow in incognito"
,
Sep 27 2017
Able to reproduce this issue on Skytap Environment on Windows machine with chrome #61.0.3163.100 It is regressed between M60 & M61 Observations: 1. In M-60 #60.0.3112.101, i can see the "Allow access to file URLs" in chrome://extensions/ 2. In M-61 #61.0.3163.79, i didn't see the "Allow access to file URLs" in chrome://extensions/ Attaching the screen-casts for reference.
,
Sep 27 2017
Lopping to folks involved.
,
Sep 28 2017
Devlin, I see you touched this a lot. Any idea?
,
Sep 28 2017
This was the result of revision a15e92ad1b93e1cef860f7a2f4247f110277e946, in order to hide the setting if the user is unable to change it, so in that respect, it's WAI. I'll let nrpeter@ chime in for that. That said, I wonder if it would be better to display the control, but disable it with a policy indication explaining it can't be modified. I don't know that we'll do that for the current page, but something to think about for the MD version.
,
Sep 29 2017
For more context around this change, check out crbug.com/173640 While the "Allow access to file URLs" checkbox was visible for force installed extensions and users could check the box, it wasn't having any effect. When the box was checked Chrome looks whether the extension is force installed; if it is Chrome prevents the change. This is done to avoid having the user change a setting which could potentially alter the force installed extension's behavior. No error message was surfaced to users, so checking this box on a force installed extension appeared to work. This was confusing to users as the check mark disappeared after reloading chrome://extensions. Since the checkbox was only a source of confusion, we removed it for force installed extensions.
,
Oct 5 2017
Is there a way to set "Allow access to file URLs" when its forced installed? The extension that is being installed needs access to files on the system.
,
Oct 5 2017
Hmm... I thought we had bits in the policy to allow enterprises to specify whether a policy-installed extension could be modified, but I can't find it in the policy list [1]. nrpeter@ or pastarmovj@, any ideas? Seems like we should, or at least allow policy to specify the permissions it has... [1] https://www.chromium.org/administrators/policy-list-3#Extensions |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Sep 26 2017Components: Enterprise
Labels: M-61