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.
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!
@Dylan Carlson As an update, the "Salesforce serves the domain over HTTPS using a Salesforce content delivery network (CDN) partner and a shared HTTPS certificate" HTTPS option for sandbox custom domains unfortunately is delayed to Summer '21 (safe harbor statement applies) instead of Spring '21.
