Proxy issue with Lion

Hi Chris, checked my keychain and both the login and system keychains have the logins but I STILL get the annoying dialog popup ONLY on Safari. So it seems this problem is only confined to Safari and no other program. I am using Mac OS X 10.11.6

BIt late, but have you tried saving your credentials in the proxy settings?

System Preferences -> Network -> Ethernet -> Advanced -> Proxies

rattex that is not very useful if you have a lab of computers

I am having the same problem, big headache for it.

The prompt appears because you are configured to use a proxy that requires authentication yet you have not configured your system with the proper credentials for said proxy.

Just as you have to enter your credentials in Safari, all other processes that generate network traffic through your proxy must also have these same credentials. The prompt is generated by AuthBrokerAgent, and it is attempting to do just that.

So, you can:

1) when entering credentials in Safari, check the box to save them to your keychain

2) enter your credentials in the prompt

3) enter your credentials in System Preferences -> Network -> Advanced -> Proxies

I am having the same problem, the only thing is this box pop up nearly straight away once the user has logged in and is happening for all users.

The main thing that i am stumped about is even when NO proxy details are set at all. Automatic detection and everything else is unticked the box still has our proxy details. How is this possible.

Is there any way to find out what is triggering the traffic in the first place. it can happen as soon as you log in or even if you have no internet open and just in system preferences.

We have never had this problem until 10.7

nicoisconfusion, what type of environment are you in (single system vs. client machine configured by a server)? If it's the latter, the server can configure it's clients to use a specified proxy and the clients will not be able to change that.

Even after unchecking all proxy settings in system prefs and "Apply"ing them you're still seeing this box? It may be that a background process has not picked up your proxy settings and is still trying to talk to the proxy.

What happens after you uncheck the system prefs, save the preferences (or applying them then closing out), and then restart (just for good measure)? Do you still see the box?

You could figure out what is triggering the traffic, but that depends on how comfortable you are using the Terminal app??

I found the fix. Running this will stop the box coming up at random times 🙂🙂🙂

I have been looking for this fix for at least a couple of months.

I know this is a bit tricky and i am not a technical expert..
But i found it myself and whoa it works..

1. Download Squidman and install it.

2. Run it and go to preferences and under "Parent" tab enter your proxy settings with authentication details.

3. Now, go under "General" tab and enter "3128" or any other number (four digits and greater than 1024) in HTTP Port and select cahe size as much you want and check all checkboxes.

4. Click save.

5. Click Start on smaller Squid window with a pink octopus(i love that symbol).

It will Start with a message "Squid is running"

6. Now, go to your proxy settings unser System Preferences>Network>Advanced>Proxies Tab and chech
HTTP, HTTPS, FTP and for each enter proxy as "127.0.0.1" or "localhost" and port "3128" (or the number you entered in HTTP Port earlier.

7. Thats, the best point, DONE!

Basically you are running a Squid proxy server on your system and now web content reaches you via two proxy servers, one of your corporate and the other on your system. You may think that this might slow down your connection as there are two proxy servers involved. My friend that is 100% correct. So a solution.

While selecting cache size remember to keep it above 1 GB. Believe me at first your internet would lag a bit, but after about 10 hours of usage it would be faster than ever. Atleast for me this has happened.

One important thing the use of other proxy server here doesn't mean that you are anonymous to the corporate proxy server as some programs like "Tor" or "Hotspot Shield" does. It simply creates another layer of proxy server. IP address spoofing is not the thing done here.

Any further queries will be greatly acknowledged.

I have done this for about 3 days and trust me that irritating Dialog never appeared. Not, even a single time.

Good Luck!

Unfortunately it does not work for me

It is still popping out the same window now asking to autenticate the proxy: 127.0.0.1:8080

this is realy annoying!!!

in any case, thanks

TRY ENTERING THIS INTO TERMINAL.

SUDO REBOOT

This post provides a durable solution where the address is a real proxy server (won't help the request to authenticate to 127.0.01. issue, that probably needs a shift-restart and other hard work)

Usually a proxy authentication dialog allows the user the option to 'allow once' or 'always' etc, and to save the proxy login details to the user's login keychain.

But under both 10.8 and in particular 10.9 whenever a proxy is in use, the user gets bombarded with multiple recurrent proxy authentication dialogs without any save options and without any identifier.

Using the terminal command nettop, I discovered that the offending dialogs come from system processes, most notably syncdefaultsd. (How to do this at the end of the post)

The problem is that syncdefaultsd is not keychain aware. It needs access to the user's proxy settings at regular intervals, but can't get them from the user's login keychain. It's proxy request dialog does not have the option to save the details to the user's keychain, and worse still does not identify syncdefaultsd as the requesting process. Even if you open your login keychain to allow any application access to your proxy, syncdefaultsd will still keep asking for your proxy details.

The solution is to ensure that you have working proxy settings saved in the *system* keychain, not just your personal login keychain.

So when you next get one of these dialogs:

1. Note the server name that is requesting authentication, the port (usually 8080) and if it is an http or https request. Typically it will be something in the form https://someproxyserver.someorganization.com:8080

2. See if you already have an entry for that server in your login keychain. If not, make one manually, (being sure to enter the whole thing as per the example above with the :8080 at the end). Typically that there needs to be two separate keychain entries per proxy server, one for http and a second for https, though syncdefaultsd only uses https.

3. Once you have login keychain entries for the proxy server, double-click them and ensure that under Access all applications are allowed, and that your user name is saved.

4. Now for the fun bit. Option-drag and drop these entries into your system keychain. Click on the system keychain, and confirm that they are there, and that all the settings are exactly right.

For good measure, do a shift-restart then a normal restart.

You should now get no more annoying dialogs for that particular proxy server. If your proxy server has more than one alias, or if you have several, then whenever you get a new unidentified dialog, repeat the above.

I discovered it using the terminal command nettop, typing into the terminal:

nettop -m tcp

This lists all active network processes. If you quit all apps you should still see quite a few network processes. If you see syncdefaultsd, wait for it to go away, or kill it via the Activity Monitor. If you haven't done the fix as above, and you open Safari, you'll see syncdefaultsd open shortly after Safari, and the annoying dialog immediately appears. After the fix is implemented, the dialogs don't appear when syncdefaultsd tries to start up.

Hope this helps someone, and that Apple fixes it in 10.9.1

Cheers

Chris.

The reason Squidman works is that it properly handles all proxy requests, including those from system processes like syncdefaultsd.

But Squidman is a *major* install. It is a full-on proxy server for server machines, with non-trivial overhead and complexity. It is way overkill for this problem.

If my solution works and you've installed Squidman, wait a bit to be sure, but I strongly suggest you remove all trace of Squidman once you know you're OK again..

Cheers

Chris.