New issue
Advanced search Search tips

Issue 592791 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Chrome FTP Access through SSO proxy

Reported by rse...@canaltacontrols.com, Mar 7 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. Ensure proxy is set in I.E 
2. Use I.E to visit any FTP site, works fine
3. Use Chrome, get "access denied authentication failed"

What is the expected behavior?
Chrome does not appear to pass windows credentials when accessing an FTP site through the proxy, this has been a problem long before the version I'm currently running. SSO for http and https works fine

What went wrong?
Ensure proxy is set in I.E 
Use I.E to visit any FTP site, works fine
Use Chrome, get "access denied authentication failed"

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 20.0 r0
 
Components: Internals>Network>FTP
Labels: Te-NeedsFurtherTriage
Status: Untriaged (was: Unconfirmed)
Asanka:  I assume that's because the IsReadyToRestartWithAuth logic used in the codepath to get system credentials is all in  URLRequestHttpJob::NotifyHeadersComplete, rather than in code shared with URLRequestFtpJob's authentication path.
Cc: asanka@chromium.org
Components: Internals>Network>Auth
Oops.

Asanka:  I assume this is because the IsReadyToRestartWithAuth logic used in the codepath to get system credentials is all in  URLRequestHttpJob::NotifyHeadersComplete, rather than in code shared with URLRequestFtpJob's authentication path.
Hoping this would be looked at...Bueler....Bueler?
So.....2018 and we have a browser that can't use SSO for the FTP protocol? Is this going to get looked at?

Comment 6 by mmenke@chromium.org, May 16 2018

Status: WontFix (was: Untriaged)
As the position of the network team is that FTP is a deprecated protocol, and is maintenance mode only, this isn't going to be fixed, unfortunately.
Depreciated protocol....lol. My network team is quickly moving towards google being a depreciated service.
The position of the network team unfortunately does not reflect the reality for many people, that FTP is still a widely used protocol, often critical to use-cases and business operations.  Though I'm not really expecting it, I hope that this stance will be re-considered at some point.

Sign in to add a comment