We are increasingly using, or being required to use, SSL-encrypted sessions (or technically, TLS-encrypted sessions) for application services. In technical terms, because the Fully Qualified Domain Name (FQDN) in the Uniform Resource Locator (URL) used by a client to access a service needs to match the Common Name (CN) in the certificate used by that service, we potentially have a proliferation of certificates (at least one per server) that need to be available to clients
One approach to addressing this proliferation is to use wildcard certificates that match multiple FQDNs within a domain. Below is a discussion on generating self-signed wildcard certificates as a way of addressing this
What