Security Certificate Errors: Known Issues with Wildcards
Almost all servers, devices, services, and platforms work very well with SSL wildcards, but there are a few known incompatibilities. These issues are not something specific to our certificates, but are rather due to problems with the way the wildcard character is handled.
The following is a list of known wildcard issues -
-
Barracuda Spam Firewalls can only create a certificate with a name that matches the server name. Technically, you can workaround this issue by naming your server in the *.domain.com format.
-
Microsoft Exchange 2007 with IMAP and POP services will not work.
-
Microsoft Office Communication Server does not accept wildcards.
-
Microsoft Outlook cannot use RPC over HTTP with a wildcard containing SSL certificate (will continually prompt for password).
Otherwise, Outlook handles wildcards perfectly.
-
Oracle Wallet Manager does not accept wildcards.
-
Windows Mobile 5 devices cannot use wildcards, Windows Mobile 6 and above work perfectly.
While this list is not intended to be comprehensive, keep in mind that most devices or applications will accept wildcard certificates unless explicitly stated otherwise in the product's documentation. Learn more about Wildcard SSL certificates.
