Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

proxy authentication required dialog not going away

I have had a first generation MacBook unibody (not yet named MacBook pro) 13", and have been using it perfectly for 4 years. I rely on HTTP and HTTPS proxy heavily to browse web, due to certain filterings in my country.


I use Google Chrome's ProxySwitchy plugin to switch to my proxy (it's a squid proxy) and it uses scutil to change the systemwide proxy. My proxy requires authentication. Now I had no problems on my mac never ever,


But i've moved to a Retina mac a couple days now and whenever I enable this proxy, the proxy authentication required dialog bugs me so much I'm forced to disable proxy and be unable to use this new mac. It seems that all sorts of applications trigger this and it happens like once or twice every minute, and only for HTTPS proxy.


There's no remember me box or any options in keychain to make it not happen, and I have to type in a long username and password everytime for every app to work, sometimes even when I open a tab in google chrome it pops again!


If someone could not help me with this, I'd have to dump this new Retina mac and have a very bad memory of it.



User uploaded file

MacBook Pro with Retina display, OS X Mountain Lion (10.8.1)

Posted on Sep 9, 2012 8:54 AM

Reply
Question marked as Best reply

Posted on Nov 19, 2013 5:27 PM

Do not use the suggestion to unload the notification center, and don't use squidman.


First try this solution, which is simpler and better.

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.

38 replies

Mar 5, 2014 3:10 PM in response to ctzsnooze

Thank you ever so much for this ctzsnooze. I am new to OSX and Macs in general, without your help I would have been fustrated for decades! The proxy I setup is university related, therefore I have installed it also on my iPad as I take it to lectures on a daily basis. However, on my iPad the problem persists (i am bombarded with authentication requests every 30 seconds). Is there a solution to this? If so, how would I go about it?

Thanks for your help in advance.


Christopher

Mar 5, 2014 4:49 PM in response to AbiusXX

Hi Christopher -


I have an iPhone inside the same network as my MacBook, using the same proxies. Although the MacBook had issues with repeated proxy dialogs, the iPhone was never affected with the same problem. This experience was the same for all our users, only MacOSX, not iOS users, were affected.


So maybe your issue on the iPad is different? Once proxy settings are saved in the iPad, you should not have to keep re-entering them. If you keep having issues with the iPad, I would suggest some of the basic resets, including rebuilding your network connection settings cleanly from scratch.


Sorry I can't be more helpful at this point.


Chris.

Mar 5, 2014 4:56 PM in response to e.a.t.

@e.a.t,


Your suggestion, if I understand it properly, is to select the hard disk itself, then use the Finder to allow user-level read-write access to all files on the entire hard disk? In practice this would put an inherited ACL at the root level of the machine allowing you to read, write and delete any file on the whole machine (including other users).


I can imagine that this would fix the dialog issue.


However, it would be extremely hazardous from a security perspective, because it allows any person with your user access the ability to wreck your entire machine. I would not recommend using this approach as it circumvents most of the major security features of the machine.


Chris.

Mar 12, 2014 3:17 AM in response to AbiusXX

Dear Chris,


The proxy server provided to me by my institute doesn't require authentication so I don't have the same problems as you guys with multiple annoying requests for authentication.


However, Safari still ignores proxy settings. I tried the Squidman solution and that failed too. Mozilla works fine though.


Any ideas why?


K.

Mar 13, 2014 2:46 AM in response to Kinster

I can't give you a specific answer, but it sounds like it could be a Safari specific problem, perhaps corrupt preferences, perhaps cache issues. In general I'd:


- make a new user and see if they have the same problem (rules out user level prefs issues)

- do a shift restart

- clear all caches manually and restart

- look in console for clues

- consider clearing all network settings by clearing Library/SystemConfiguration

- consider temporarily disabling all internet plugins (put in a different folder)

- considern clearing all DNS caches


All the above is fairly generic advice... not specific, exactly, to your problem, but could help clear an issue that perhaps might cause your problem.


Chris

Apr 10, 2014 5:04 PM in response to ctzsnooze

Hi Chris,

your solution works quite well for single user of a macbook or imac. But we are having this same issue on a shared iMac. Which means we can't store the keychain info into the System area as all users will then be able to easily see the password used for proxy authentication.

Is there a way to make your solution work on a shared machine without compromising the security aspect as described above.

at our work we are behind a proxy that requires authentication and that authentication is based on AD accounts credentials.


thanks

Apr 10, 2014 7:37 PM in response to Aerys Targaryen

Hi Aerys


Good question.


Maybe you could test this... If the system keychain entries are stored by an admin user, is an admin level password required to view the password? If so, then your shared users could be configured as non-admin users, and they would not be able to open the keychain entry.


It also may be possible to more severely restrict access to these passwords using the unix chmod terminal commands, say to something like only root/wheel for read access, denying everyone else. I use batchmod for this. Depending on those settings, with an admin password might still be able to access them but there are bits of the system that even an admin can't easily read so you could set permissions very strictly if needed. The downside is that this might make these entries difficult to delete later on....


Please let us know what works for you - thanks!


Chris.

proxy authentication required dialog not going away

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.