GNOME Bugzilla – Bug 725919
About adding proxy authentication field in nm
Last modified: 2014-10-13 14:30:13 UTC
Created attachment 271271 [details] general idea hello,Our college internet is under the proxy server i.e. connection is done through proxy server,So we have use our college id and password for accessing the internet service. But I think there should be option in network manager of authentication field also ,alongside proxy address and port no. i.e there should an check box to enable/disable the authentication field. and below that checkbox-->there should be two text field (User Id: and Password:) and Button for applying it throughout the system. Advantages: #for new user, it will be very convenient way to use the connection system wide. instead of editing /etc/environment file and adding the proxy setting. #system wide proxy setting enables the user to use all the application without configuring it separately.(eg.synaptic manager,irc client,mail client,browser,etc) I think this feature can really helpful for the users. please review on this. regards, prasad mhatre.
That would be a great improvement, not having the ability to add credentials to the proxy settings causes any application that does not ask for credentials like gnome extensions, not to work. Changing /etc/environment does not always work in my experience, sometimes it gets overwritten by gnome nm settings. Also, how did you get the ignore hosts box in the settings? Thanks, David Twersky
i am using debian testing (jessi).and it is having that option by default. can anyone call up the developer and ask how can this be done. and yes, i too have the same problem with gnome-extensions , but that doesn't concerned much for me.
This UI field from the screenshot is not related to NetworkManager. NM doesn't manage proxies. Reassigning to gnome-control-center
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 646354 ***