09-25-2020 08:38 AM
09-25-2020 08:38 AM
On Version 85.0.564.63, ExternalProtocolDialogShowAlwaysOpenCheckbox is not working. Any alternate approach.
I am trying to force open button click for each protocol requests.
09-25-2020 04:37 PM
@anilrepala Hi! Thanks for reaching out! You mentioned the policy is not working on Version 85.0.564.63. Is it the case that it was working previously and after a recent update it stopped working? If so, can you please submit detailed feedback and diagnostic data through the browser, if you haven't yet?
If you are trying the policy for the first time, can you provide a little more details about the issue you are running into and what you are trying to do? Do you have a screenshot?
09-28-2020 05:49 AM
HI @Kelly_Y, Last time I observed it working was in version 83.
As Silverlight is getting obsolete, I have created a windows custom protocol handler which was previous handled by Silverlight application. Now, when a User clicks on a button my custom protocol will be invoked but we are getting a popup every time with open/cancel buttons to perform the action.
09-28-2020 01:28 PM
@anilrepala Hi! The policy was restricted to only work from secure (i.e. https) pages. I believe the change was made around Version 83. Can you confirm if you are using https:// links? If so, let us know and we'll loop in the GPO team. Thanks!
09-29-2020 02:41 AM
@Kelly_Y Hi, We are using the only HTTP:// links. As per your comments, we can't surpass the pop-up for HTTP:// links but can we make the 'Open' button as default instead of the 'Cancel' button?
09-30-2020 07:03 AM
@anilrepala505 For security reasons (to avoid gesture hijacking attacks), it is important that the default button remain Cancel. However, administrators are able to preapprove Origin/Protocol combinations using the AutoLaunchProtocolsFromOrigins policy, and non-secure HTTP origins may be specified there at the administrator's discretion.
More discussion of this area can be found in my blog post.