--proxy-server= on command line ignores username and password auth
Reported by
julianga...@gmail.com,
May 31 2016
|
||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
URLs (if applicable) : [internal proxy server]
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: N/A
Firefox:
IE: N/A
What steps will reproduce the problem?
(1) Run Chrome with the command line switch --proxy-server against a proxy server that requires username/password auth and pass the values into Chrome on the command line. https://www.chromium.org/developers/design-documents/network-stack/debugging-net-proxy
(2) Check whether the username and password appears in chrome://net-internals/proxyservice.config#proxy
(3) Check an external site to see if it uses the proxy without doing a proxy popup
What is the expected result?
(a) That the username and password is displayed in chrome://net-internals/proxyservice.config#proxy
(b) Browse external site to see if it uses the proxy without doing a proxy popup
What happens instead?
(a) The username and password is not displayed in chrome://net-internals/proxyservice.config#proxy
(b) Browse external site and it does a proxy popup
Please provide any additional information below. Attach a screenshot if
possible.
This person can reproduce the issue here:
http://superuser.com/questions/902620/google-chrome-proxy-settings-with-username-and-password?rq=1
This person can reproduce the issue:
http://superuser.com/questions/83007/configuring-proxy-settings-for-google-chrome-on-linux#comment84860_83062
I'm running the Chrome Browser in Docker from here:
https://github.com/SeleniumHQ/docker-selenium/blob/master/NodeChromeDebug/Dockerfile
,
Jun 2 2016
Don't think we've ever supported this.
,
Jun 17 2016
Matt is correct, this is a feature request not a bug. Note that contrary to comment #3 Chrome does not and has never supported specifying the proxy credentials from within the PAC file. The closest related feature request is issue 16709 for pulling credentials from environment variables or gconf. In general I am not excited about this sort of proposal. Putting credentials in plaintext stores like commandlines is IMO an anti-pattern, and not something we want to encourage. I think proper solutions to this problem involve storing the credentials in chrome's password manager, or a system key store. Is this something you want for testing purposes?
,
Jun 21 2016
I take your point about not wanting to do this - as it is fundamentally insecure. For whatever reason - Microsoft have gone down the path of making this an option (as an alternative to Active Directory security) for Network proxy configuration. IE does work this way. Thanks - I got stuck in a situation with an AWS VPC connecting to a Windows network for external access. (Standard big Corp setup). I wanted to use Chrome inside Docker for Web-driver driven testing (Selenium Grid style). For other people that stumble across this - what solved my problem was https://github.com/sjitech/proxy-login-automator. (ie the Docker Container for Chrome we use starts this up in the background).
,
Jun 21 2016
Moving to WontFix. |
||||
►
Sign in to add a comment |
||||
Comment 1 by mef@chromium.org
, May 31 2016