Certificate validation for custom https domains fails when a certificate contains a subject alternative name list that has no DNS entry items in it
Last updated 2016-12-08 ·Reference W-2974340 ·Reported By 0 users
A customer noticed that the validation fails when they attempt to link to their domain a certificate that has a subject alternative name list that has no DNS entry items in it. As it turns out, the main web browsers -- Firefox, Chrome, and IE8+Win7 (others can be tested, too) -- fall back to the certificate's subject common name (CN) in that scenario. The validation code within Salesforce, however, does not perform that fallback.
when you attempt to link to your domain a certificate that has a subject alternative name list that has no DNS entry items in it.
either not having a subject alternative name list or including a DNS entry that equals their CN in the subject alternative name list.
Reported By (0)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.