Chrome feature request: Add policy to control External Protocol Handlers handling |
|||||||
Issue descriptionSummary: User needs policy to be able to set Chrome Browser to run external protocol handler applications (in this case Citrix Receiver, receiver: ) without confirmation from users, not even once-shown dialog with "Remember my setting". Use case / Motivation: Improve user experience, neutralize possibility of human error (eg clicking on "don't open" and remembering this setting) via centralized setting for all users. Existing workarounds: Editing Preferences file for user in local profile. Case#: 13469955
,
Sep 6 2017
Matt, I know this is on your radar for browser. Do you have any idea how this can work with ARC++ apps? +Elijah to shed more light on how this would work with ARC++ intents. Overall, if we solve this, we should for ARC++ apps and not for Chrome apps.
,
Sep 6 2017
This technically possible on Windows today via URL whitelist. We will do a better job documenting this. Can we clarify/narrow the scope of this to Chrome OS + ARC++?
,
Sep 6 2017
I have actually already tried adding 'receiver:*' to the URLWhiteList policy and it did not fix the issue.
,
Sep 6 2017
From the testing I've done, the policy in question would need to effectively manipulate the 'excluded_schemes' section under 'protocol_handler' in the Preferences file. Once I add a line for "receiver": false, it works as desired. This has been tested mostly in version 60.0.3112.113 of Chrome on Windows 7, 10, and Server 2012R2.
,
Sep 6 2017
,
Sep 6 2017
We have found the root issue and the work-around for the near term. Please add something to the URLblacklist such as "foo:*" and the proper URLWhiteList should begin to work. Please share your findings. Thanks
,
Sep 6 2017
Original issue was for Windows browser, Mac/Linux possibly affected as well, not sure if ARC++ is using same schemes, sorry for misrouting.
,
Sep 6 2017
Support for external proto handlers exists in windows today via the URLWhiteList. Chrome OS + Android + Linux need to be investigated. We will add this to the help center documentation to ensure it is more easily accessible from the IT-Admin perspective.
,
Sep 6 2017
Unfortunately setting the URLBlackList as well as URLWhiteList did not fix the issue, prompt is still generated. Screenshots attached.
,
Sep 6 2017
Looks like the capital 'L' was upsetting it, windows doesnt care about case but apparently Chrome does :) Testing via GPO now
,
Sep 6 2017
Confirmed! Prompt was removed successfully with either GPO or registry values. Thank you very much.
,
Nov 11 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bhthompson@google.com
, Sep 6 2017Owner: dskaram@chromium.org