Skip to main content

Hello, we've recently joined the pilot and have four sandboxes for which we'd like to set up custom domains. For the sake of simplicity we would typically use a single SAN certificate to reduce the number of certs that need to be ordered, installed and updated every few years.  When setting this up however, we receive an error message of the form:

 

Error: The domain name dev1-www.company.com wasn't in the supported set of domain names in the certificate: sandbox-www.company.com, www.sandbox-www.company.com.

 

We've set up a single SAN cert referencing the following domains:

CN: sandbox-www.company.com

DNS Names:

sandbox-www.company.com

dev1-www.company.com

itest1-www.company.com

uat-www.company.com

pfix-www.company.com

 

We did not read anything in the pilot documentation that indicated SAN certs weren't supported and thus didn't expect it to be an issue. Can anyone here confirm whether SAN certs will be supported and if so, whether there are any specific requirements around how a SAN certificate must be set up?

 

Each cert costs money to set up so we don't have a lot of room for trial-and-error here.

 

Any help is much appreciated.

3 comments
  1. Jun 23, 2021, 7:21 PM

    Unfortunately, the Salesforce Sales, Service, and Communities Cloud doesn't yet have way to specify a subject alternative name (SAN) list within the user interface when creating a new certificate. A possible option is to create the certificate signing request (CSR) outside of Salesforce, get it signed, put the signed certificate chain and the private key into a Java Keystore (JKS) file, and then import it into the org. General documentation for creating the JKS file exists in https://help.salesforce.com/articleView?id=000339841&type=1&mode=1 .

0/9000