6

I am able to use Google Chrome under Linux Mint behind a proxy. But when the browser starts, each time I have to enter the username and password for the authentication.

Is there any way I can set the username password as I launch the browser?

I have already tried:

chrome --proxy-server="username:password@yourIP:PORT"

(e.g., chrome --proxy-server="username:password@127.0.0.1:8080")

This did not work.

  • Try setting system-wide proxy settings where you can provide the proxy address and credentials to Linux itself - justintung.com/2013/04/25/…. You can then let Chrome run without any proxy settings as Linux will do that for you. Also, if your proxy server is a Microsoft product (ISA/TMG) then you can install a package on your Linux (a .deb package) called NTLM (I Think). This has a config widow for you to provide proxy address and username/password. – Kinnectus Apr 17 '15 at 6:42
  • Thank You. That was a great help. But my issue is that, its still having problem with the authentication. I have to enter the username and password to make it work. – Antriksha Somani May 25 '15 at 10:07
  • Did you do the export as per the link I put? From your question it still seems you're putting the proxy settings as a startup argument for Chrome... – Kinnectus May 25 '15 at 11:51
  • Please star this as a bug in Chrome here: bugs.chromium.org/p/chromium/issues/detail?id=615947 – hawkeye May 31 '16 at 10:19
3

Note the following:

Proxy auto-configuration files do not support hard-coded usernames and passwords. There's good reasoning behind this too, since providing support for hard-coded credentials would open up significant security holes, as anybody would be able to easily view the required credentials to access the proxy.

Rather configure the proxy as a transparent proxy, that way you won't need a username and password. You mention in one of your comments that the proxy server is located outside your LAN, which is why you require authentication. However, most proxies support rules based on the source IP, in which case it's a simple matter of only allowing requests originating from your corporate network.

The original proxy auto-config specification was originally drafted by Netscape in 1996. The original specification is no longer available directly, but you can still access it using The Wayback Machine's archived copy. The specification hasn't changed much, and is still largely the same as it was originally. You'll see the specification is quite simple, and that there is no provision for hard-coded credentials.

To solve this problem - you can use this tool:

https://github.com/sjitech/proxy-login-automator

This tool can create a local proxy and automatically inject user/password to real proxy server. Support PAC script.

0

I tried various CLI approaches, but couldn't get it to work with authentication. However, the Switchy Omega extension works fine so far.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.