up vote 1 down vote favorite
share [g+] share [fb]

I'm working in our test lab. All the machines in our test lab are on the .foo.bar.baz.com domain. I can install our server with an SSL certificate with the common name of *.foo.bar.baz.com and it will successfully validate...

https://abc.foo.bar.baz.com
https://xyz.foo.bar.baz.com

...but will not work for...

https://abc

which is how a lot of our scripts are designed. Is there any SSL common name I can use (I tried *) that will validate sites without a domain?

link|improve this question
100% accept rate
feedback

2 Answers

up vote 1 down vote accepted

Probably the best you can do is a UCC cert that lists all of the hostnames individually. Here are instructions on generating a CSR from openssl to do this (since the standard prompts will not ask for the subjectAltName field). So you could create a certificate with *.for.bar.baz.com as the Common Name, and then list the hostnames in the alt_names section/

link|improve this answer
That solution will probably work. Thanks for the answer. – Pace Dec 9 '10 at 21:48
feedback
up vote 1 down vote

There's no such thing as a "site without a domain" unless you're accessing by IP only. In the case of https://abc, abc IS your FQDN.

There is unfortunately no way of having a certificate that does both versions of the wildcard you're after. You could work on Subject Alternate Names for each certificate, but then that obviously needs to be re-issued every time there's a new server added.

link|improve this answer
Thanks! I had to give the check to the other answer for providing the link, but this information was good too! – Pace Dec 9 '10 at 21:47
@pace - all good. DerfK probably needs the rep more than I do anyway :) – Mark Henderson♦ Dec 9 '10 at 21:58
feedback

Your Answer

 
or
required, but never shown
discard

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