Skip to main content

Greetings!



Having a bit of trouble with a host name mismatch on a ceritificate that's causing an issue with Outlook on startup.





So far, I've added and exported the certificate in Keychain Access, uploaded it to the JSS in a configuration profile, and then tried to deploy it to a test computer but the problem here is that the trust settings are set to Use System Defaults.



Then, I tried packaging the certificate up with composer and copying it to /tmp and installing it with this command:



/usr/bin/security add-trusted-cert -d -r trustAsRoot -k /Library/Keychains/System.keychain /tmp/certificate.cer


Which does add it and set to Always Trust...





However, I still see the Verify Certificate message when Outlook is opened and Use System Defaults as the Trust settings even though the certificate is marked trusted for all users.





Any thoughts on what I might be doing wrong or another way to go about adding this certificate to the keychain and setting it to Always Trust?



Thanks!

@pvcit Having the same issue, with a wireless cert that I want to deploy - export the trusted cert, add to config profile and deploy to a machine, and the user has to trust it. A different cert that I deploy, ironically, still gets trusted when deployed to machines via config profile.

@pvcit Having the same issue, with a wireless cert that I want to deploy - export the trusted cert, add to config profile and deploy to a machine, and the user has to trust it. A different cert that I deploy, ironically, still gets trusted when deployed to machines via config profile.



Few years down the line but this issue still exists. 

Terms & ConditionsCookie settings