by I have recently setup E2k and enable SSL by generating my own certificate,
several problems have come up, as follows:
1. On the PC's since the Public Folder scripts use the servers UNC name and
not the FQDN the certificate shows as invalid and returns an error. However
when using a wildcard cert. (*.microsoft.com) doesn't work either because it
returns the error, "The certificate authority is invalid or incorrect
12045". So the only way to get it working is to generate a certificate using
the FQDN and enter only the UNC name in the browser to access the server
(i.e.. https://server/exchange), which won't work across the internet at
all.
2. Using IE 5 on the Macintosh machines, there is no way to import the
certificate setup on the server as a valid root certificate authority, so it
is impossible to establish a correctly encrypted session without purchasing
a certificate.
Am I completely in the dark about how to do this correctly or are these some
serious bugs? I have tried to import our Apache key, but it doesn't include
the Private Key pair and Thawte told me the Cert. wouldn't work with IIS 5.0
because it doesn't recognize wild cards (*.microsoft.com). I have been at a
serious loss to find any decent documentation about how to setup ssl
correctly for Outlook Web Access on E2k. Can anyone answer my questions or
point me in the right direction?