Fix for Safari on Mac: Client Certificate no longer accepted, or slow authentication…

Now this is a very annoying behavior I’ve observed with Safari on Mac and accessing a variety of SAML2 protected sites – while other browsers such as Chrome don’t appear to have that problem. The authentication process may just hang, or also fail with an uninformative cookie error.

Ultimately, what helps is this: Search Keychain for “” – there’s probably one certificate starting with that name and having a longer extension:


You will see other certificates depending on it. Delete that certificate, at which point the others will show up as no longer valid:


Delete those too. You don’t even need to restart your browser. Just go back to the site where the authentication was not working, and refresh the page. It should work now.


This post currently has one response

  • Thanks for your help. Do you, by chance, have any idea what this certificate is for? I’m not having any issues accessing websites with safari, however I am somewhat suspicious when I see a new certificate created within 1 week ago, such as one with the prefix you are describing. It seems to somehow be related to my appleid. Any thoughts or further information that you can provide? Thanks in advance!

Leave a Reply

Your email address will not be published. Required fields are marked *