Custom Domains for Sandboxes

Hi @Steven Lawrance

We are participating in the pilot with a customer, and I want to thank you for the great work.

We probably found a bug in session handling in a customer community (using B2B Commerce). We are only able to reproduce it when the custom domain is enabled for the community. 

Steps to reproduce it:

1. login in to the community (either by using SSO using an OpenID Connect Auth Provider or Login As on contact) --> we are logged in, everything (also remote actions) work well
2. export session cookie "sid"
3. remove all cookies
4. reload the page --> not logged in anymore
5. import session cookie "sid"
6. reload the page 
   • without custom domain: logged in again. everything working (also remote actions)
   • with custom domain: not logged in, remote actions throw error "Remoting request invalid for your session.  Refresh the page and re-submit request" - even a reload doesn't help to recover. Removing session cookie sid helps.

The same also happens if you only modify the session cookie instead of removing and importing it.

I am also not able to reproduce this behavior on production with a custom domain enabled.

As this is very technical to reproduce the behavior, it often happens with normal user behavior browsing the community. 

I hope you can help me.

Thanks.

Thomas

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.

Hi Team,

One of the users @Raj Sookrah is making use of the pilot program"Set Up Your Sandbox Custom Domain (Pilot)" as documented in : https://help.salesforce.com/articleView?id=domain_mgmt_sandbox_custom_domains_setup.htm&type=5

As per the doc, it says that we need to setup the custom domain in production and then in 'Select sandbox in the Associated Org field.'

However, they are trying to setup custom domain directly in sandbox, by following below:

Firstly created an SSL certificate. Then created the domain and attached the certificate with the domain creation. 

Next added a custom URL for the site, lastly created the DNS.

The domain looks like: https://abc.sandbox.xyz.com and created a CNAME that points to abc.sandbox.xyz.com.00Dxxxxxxxxxx.live.siteforce.com 

Under custom URL: the status for the domain: abc.sandbox.xyz.com  is being displayed as Published. However, the redirection is not happening and the domain page does not load.

~~~~~~~~~~~

Could you please help to confirm if the above steps followed are correct or not.

If not, please help to share the exact steps to be followed to complete the custom domain setup in sandbox before moving forward for production.

Also, they are making use of domain in the format: abc.sandbox.xyz.com  - please confirm if this is a right format for domain or not.

Many Thanks

Hi @Steven Lawrance 

We would appreciate your thoughts on the behavior we’ve noticed setting up custom domains.

In our production instance, we were able to create the two domains below.  Both are configured using  ‘No HTTPs’ since we don’t have certificates for them.

    -  shop.bluebeam.co.uk

    -  testshop.bluebeam.co.uk

We created DNS entries for both domains and pointing to our Salesforce production instance:

   -  shop.bluebeam.co.uk.00****************.live.siteforce.com

   -  testshop.bluebeam.co.uk.00****************.live.siteforce.com

In our sandbox,  we created two custom URLs (using the two mentioned above) pointing to the same community.  When we use shop.bluebeam.co.uk,  the page redirects to our sandbox  https://b2bpilot-*******.****.force.com/ourhomestore

Questions:

a) After the page is redirected,  it displayed the sandbox URL.  We were expecting the page URL to be https://shop.bluebeam.co.uk/ourhomestore.  

b) For our communities SSO, we have an Auth Provider setup.  In the same sandbox, we noticed that the Auth Provider URLs under the community section were not updated to reflect the custom URLs we created.   If we have multiple custom URLs pointing to the same community,  what will be the URL used in the Auth Provider —> Community?

Thanks!