Chrome 62 .adm GPO Setting of "Content Settings/Default Flash Setting" is not working properly
Reported by
gab...@gnasd.com,
Oct 30 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Example URL: Steps to reproduce the problem: 1. In a domain environment configure the GPO option in User Configuration/Administrative Templates/Classic Administrative Templates/Google/Google Chrome/Content Settings/Default Flash Setting -> Enabled (Allow all sites to automatically run the Flash plugin.) 2. Go to any website that tries to display or access Flash content. Like https://helpx.adobe.com/flash-player.html 3. Flash player will report as disabled. And since the setting is now "managed by administrator" users cannot override the setting to enable it themselves. If the user goes into Chrome Settings/Advanced/Content Settings/Flash, Flash will report as "Ask first" and be greyed out from change because it is now "Enforced by your administrator." What is the expected behavior? When the GPO .adm setting in "Google/Google Chrome/Content Settings/Default Flash Setting" is set to "Enable/Allow all sites to automatically run the Flash Plugin", Flash should be enabled on all websites. Instead it is set to "Ask first." What went wrong? It appears as though the setting of "Default Flash Setting -> Enable/Allow all sites to automatically run the Flash Plugin" is hard setting the Chrome browser to "Ask first" instead of actually setting it to Allow all sites to run Flash, but since the setting is now "managed by administrator" users cannot make changes to the setting. Does it occur on multiple sites: Yes Is it a problem with a plugin? Yes Flash Did this work before? Yes At least 59 and prior. Does this work in other browsers? Yes Chrome version: 62.0.3202.75 Channel: stable OS Version: 10.0 Flash Version: 27.0.0.183 This is with the latest version of the Chrome 62 Admin Templates targeting major version 62.
,
Oct 31 2017
Able to reproduce the issue on Windows 10 with chrome #62.0.3202.75, followed the steps as mentioned in the comment #0 On updating the policy in client machine, observed that in chrome://settings, flash settings is showing Ask First, whereas in M-57 version by enabling this policy, flash content is played by default This is a regression issue, attaching the screen-cast for reference. gabelj@ Could you please look into it and confirm that M-57 is expected behavior & M-62 is a Actual response
,
Oct 31 2017
This isn't a regression, it's working as intended. In Chrome 62 we removed the option to always run Flash Player, due to the security and privacy implications of that setting. Enterprise admins can still add policy entries (including wildcards) to PluginsAllowedForUrls (1). To achieve similar behavior one could add an entry for "http://*" and "https://*". https://www.chromium.org/administrators/policy-list-3#PluginsAllowedForUrls
,
Nov 1 2017
,
Nov 15 2017
,
Nov 15 2017
@ericde@chromium.org I think you are missing the point. The issue isn't that the DefaultPlugins policy is now removed. It's that if the policy is set, it prevents users from adding Plugin Exceptions locally. Can someone please re-open this bug?
,
Nov 17 2017
In 779630-M62.mp4 try and add an exception for Adobe's site. It won't work. |
|||
►
Sign in to add a comment |
|||
Comment 1 by manoranj...@chromium.org
, Oct 30 2017Components: -Blink Enterprise Internals>Plugins>Flash
Labels: Needs-Triage-M62