Quote:
Originally Posted by jterhune 1. Is it true that I cannot simply use the admin web console to install the certs? If I need to (or want to) install via command line, where would be the appropriate place to find documentation? I found documentation for self signed multi-server and commercial single server, but nothing for commercial multi-server. |
The admin interface is handy, but does not work in all situations we have encountered. I would recommend getting comfortable with the CLI tools for cert management, it is actually less confusing in the end. I also believe that for the proxy server you have to install it via CLI.
Quote:
|
2. If I really just want a commercial cert for https, is a cert for mail.domain.edu enough? Is the install process different?
|
You only need a cert for the domains to which clients are connecting. So if you have a bunch of mail stores on the backend, but they are all serving mail.domain.edu through the proxy, you only need a cert for mail.domain.edu.
Quote:
|
3. If we want commercial certs for everything else, do I need to generate separate certs for zcs-ldap.domain.edu, etc as well as a seprate one for https?
|
You can keep all the internal communication using the self-signed certs and only use the commercial cert for the web-client access that actual users will be hitting.
Quote:
|
4. Do I need (or should I get) a wildcard cert?
|
From my personal experience, I would avoid wildcard certs. Browsers do not handle them in a universal manner, so you are likely to get varying results.