Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm reading about how to install SSL in the library. Why would one choose the commercial approach over the subjectaltname approach? The subjectaltname approach allows the flexibility to host multiple secure DNS while the commercial approach does not. So why not just stick with the subjectaltname approach?

share|improve this question
up vote 1 down vote accepted

If you have multiple sites to secure on one server, using SubjectAltNames (with a SAN or UC SSL certificate) is a great solution. It is slightly more secure to use separate certificates for each site, but the difference is negligible in most cases.

share|improve this answer
Sometimes in Firefox, I get a warning message about an SSL and it asks me to make an exception before proceeding. Do you know if issues of this nature will exist with the subjectaltname approach? – John Feb 22 '10 at 1:43
No, they won't exist. – Robert Feb 22 '10 at 15:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.