New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 633789 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Whitelist / support TBAuth protocol handler in Chrome

Reported by kevin.st...@gmail.com, Aug 3 2016

Issue description

Chrome Version       : 51.0.2704.103
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: FAIL
  Firefox 4.x: FAIL
     IE 7/8/9: OK

What steps will reproduce the problem?
1. Log onto a Windows 10 machine. 
2. Launch Chrome
3. Visit a web site that makes a TBAuth call. For example, http://tbauth-server1772.cloudapp.net/client/login.html
4. 'External Protocol Request' dialog box appears with the following actions: (1) Launch Application, (2) Do Nothing, (3) Remember my choice for all links of this type.

What is the expected result?
I would expect that this protocol handler is white listed so that I never see this prompt. For example, when I click on the mailto protocol handler, it simply opens up my default mail client without a prompt.

What happens instead of that?
A prompt appears that requires me to either (1) Launch the Application or (2) Do Nothing. I also have the option to "Remember my choice for all links of this type".

Please provide any additional information below. Attach a screenshot if
possible.
Screenshot attached.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
 
tbauth - External Protocol Request.PNG
31.2 KB View Download
In terms of whitelisting, we'd like to include both: “tbauth” and “windows.tbauth”

Comment 2 by mattm@chromium.org, Aug 3 2016

Components: Security>UX Internals>PlatformIntegration
Labels: Needs-Bisect
Cc: jsc...@chromium.org rpop@chromium.org
Labels: -Needs-Bisect
Status: WontFix (was: Unconfirmed)
 Issue 601725  already exists to improve this dialog. We are not expanding the list of protocols to whitelist. The only protocols that should be whitelisted are historical, as they have never prompted in any browser (e.g. mailto:).
Components: -Security>UX
Labels: Team-Security-UX
Security>UX component is deprecated in favor of the Team-Security-UX label

Sign in to add a comment