I know that an SSL wildcard certificate (
*.example.org) can be used to support many names under the domain (
c.example.org). I also know that the * is only good for matching a single level of name. That is,
*.example.org will not work on
What if I used a certificate with the name ..example.org? I'd like to build a certificate with the following name configuration:
CN=example.org subjectAltName=DNS:example.org, DNS:*.example.org, DNS:*.*.example.org, DNS:*.*.*.example.org
I've tried building a few like this as self-signed certificates, but I've not had good results. For example, chrome tells me "Server's certificate does not match the URL."
Is it possible to have nested wildcards in a certificate, or do the popular browsers not support this?
edit I believe it's possible to build a cert like this: I've done so with OpenSSL. It just looks like browsers understand it. I was hoping for confirmation of that, or if I'm lucky, a "here's how you do it."
*.app1.example.com, but if I could get a cert with
CN=*.example.com, SAN=[example.com *.*.example.com], I could put that on a load balancer and have it work for most situations.