pasobover.blogg.se - Godaddy certificate for citrix on mac

#Godaddy certificate for citrix on mac for mac
#Godaddy certificate for citrix on mac mac

#Godaddy certificate for citrix on mac mac

Citrix works fine for me if I connect through the iOS app or through the Chrome Citrix App (from the same Mac that I'm having difficulty with).

#Godaddy certificate for citrix on mac for mac

Nobody else is having this problem at work with Citrix Receiver for Mac (even with the same base configuration as me).

This also didn't work in Safari or Chrome. This didn't work in Safari or Chrome, so I renamed them as *.crt files.

/HDD/User/Library/Application Support/Citrix Receiver/keystore/cacerts.

/HDD/User/Library/Application Support/Citrix/keystore/cacerts.

So, I exported both the intermediate and root certificates and placed them (as *.cer files) in the following locations: I tried to connect in Chrome (I typically use Safari), it didn't work either. I already had the root certificate in my keychain, but it was set to default trust values, so I marked it as trusted for all purposes. I did not have the intermediate certificate in my keychain, so I grabbed it and added it without issue.

VeriSign Class 3 Public Primary Certification Authority - G5 (root certificate).

Symantec Class 3 Secure Server CA - G4 (intermediate certificate).

However, when I trace the chain of SSL certificates, at the URL where I connect to Citrix, I get the following chain, which contains a similarly named root certificate, but one that doesn't exactly match the error that I've been getting: "/C=US/ST=/L=/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority/CN=" In particular, the certificate that I have apparently chosen not to trust is this one: I'm running the latest version of macOS Sierra and the latest version of Citrix Receive for Mac.

After connecting to my office's Citrix environment for years via Citrix Receiver for Mac without issue, I have (apparently) randomly begun to get the "SSL 61 Error", where Citrix complains that I have chosen not to trust the issue of the server's security certificate.