Extension Whitelist not overriding Blacklist
Reported by
lambe...@spr.k12.oh.us,
Feb 7 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Configure policy ExtentionInstallBlacklist to "*" 2. Configure policy ExtentionInstallWhitelist to "mloajfnmjckfjbeeofcdaecbelnblden" to allow Snap&Read extension. 3. Attempt to install Snap&Read What is the expected behavior? Snap&Read should be allowed to install. What went wrong? Getting error that the plugin is blacklisted. Did this work before? N/A Chrome version: 55.0.2883.95 Channel: n/a OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 24.0 r0 I can set individual values on the blacklist to black specific extensions and that works, when I attempt to only allow certain extensions is where I am running into problems. When I check chrome://policy both policies show correctly and status is ok
,
Feb 11 2017
Tested the policy in a Window client server environment. On the server: 1. Configure extension installation blacklist to"*" 2. Configure extension installation whitelist to "mloajfnmjckfjbeeofcdaecbelnblden" 3.On the client side :Installed "Snap &read" extension Chrome Version : 56.0.2924.87 I was able to successfully install the extension, don't have a mac client setup for testing at this moment. Also you are running older version of chrome, could you please upgrade and update the thread.
,
Feb 20 2017
,
Aug 18 2017
mzheng@ can u check if this is still happening. I can't imagine such a bug still being open for so long.
,
Aug 18 2017
Tested the policy in a Window7 & Win 10 client server environment. On the server: 1. Configure extension installation blacklist to"*" 2. Configure extension installation whitelist to "mloajfnmjckfjbeeofcdaecbelnblden" 3.On the client side :Installed "Snap &read" extension Chrome Version : 62.0.3189.0 I was able to successfully install the extension, don't have a mac client setup for testing at this moment. lambeskp@ Could you please confirm whether this issue is still exists in latest chrome stable. Thank You...
,
Aug 18 2017
Closing, please reopen if the issue persist. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Feb 8 2017Labels: Needs-Milestone