[fuigo]

I’m also quite confused with all this SSL certificate business on Mac OS X Server 10.5.4 now.

We ran a test environment on a self-signed certificate for months. We instructed test users to ignore the insecure certificate warning when logging on for wiki, ichat, etc. Test users on Macs, we were able to simply force-trust the self-signed certificate to rid of the warning message every time they log on.

Eventually, the company purchased a Verisign-signed certificate. We received a cert.cer file, which contained the CSR code. We were under the impression that we could simply select the current self-signed certificate created on Mac OS X Server and use the “Add Signed or Renewed Certificate from Certificate Authority…” function to import the Verisign CSR code to our existing certificate. Well, to sum it up, nothing worked.

The certificate is still self-signed. We repeated the same steps a few more times. On a few runs, the original certificate simply disappears from the list. Interesting…

Some info that I found on Verisign’s own site: [url=https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=S:SO5328&actp=search&searchid=1218086860551]HERE[/url]

Any ideas?

[fuigo]

Thanks for helping out!

My IT department is psyched as it learns each day what wonderful things that Mac OS X Leopard Server could offer right out of the box. There are talks of running a simply OS X server now and using the AD to administer only the task-specific PCs at work!

Is there any obvious downside of running mainly Macs?

[Author]

Posts