When app/ext is removed from force-install policy, do NOT uninstall unless it is included in blacklist |
|||||
Issue descriptionWhat is the expected output? This is the planned behavior, but we need to modify it. Hence marking as feature. When admin removes an app/ext from force-install, it automatically is uninstalled from user's Chrome What do you see instead? This uninstall should happen only if the app/ext is in blacklist, e.g. apriori through a blacklist definition like *
,
May 10 2016
BTW, we tested this on M52, and found that three of the four scenarios pass. The failure happens when "Allow or Block All Apps and Extensions" is set to "Allow all apps and extensions except the ones I block", and the app is *not* blocked. The failure is that when the app is removed from the force-install list, it is removed from the CrOS device. However, you can install again, as it is allowed. Expected behavior is that, since all Apps are allowed (and the removed app is not blocked), it should remain installed. I think the failure should be treated as a bug. Here are the four scenarios we tried: 1) Removed from Chrome OS when "Allow or Block All Apps and Extensions" is set to "Block all apps and extensions except the ones I allow", and the app is *not* allowed. -- Pass 2) Removed from Chrome OS when "Allow or Block All Apps and Extensions" is set to "Allow all apps and extensions except the ones I block", and the app is blocked. -- Pass 3) Not removed from Chrome OS when "Allow or Block All Apps and Extensions" is set to "Block all apps and extensions except the ones I allow", and the app is allowed. -- Pass 4) Not removed from Chrome OS when "Allow or Block All Apps and Extensions" is set to "Allow all apps and extensions except the ones I block", and the app is *not* blocked. -- Fail
,
May 10 2016
Great analysis Scott - and agree with your recommendation.
,
Dec 10
James, this looks like a possible request for you to look at
,
Dec 11
Thanks. Added this to the extensions platform backlog and marking the bug as available. We'll circle back here if/when this gets picked up.
,
Dec 11
I believe the experience administrators expect is that force-install is basically the way to determine which items should be on there. The reason I believe we remove the extension or app is because what if admin accidentally force installs X - then they realize they don't want it there. By removing it from the list, things would go back to the way they were. Max can probably confirm this behavior. If things are working as intended, we can close this bug.
,
Dec 11
Correct. I think we can close this as WAI. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by scunning...@chromium.org
, May 9 2016Owner: maxkirsch@chromium.org
Status: Assigned (was: Untriaged)