528
edits
Installing 3B Docs: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 100: | Line 100: | ||
Now that you have set up a Site/Digital Experience, you will need to grant the "guest user" (default user assigned to people interacting with the site) with the correct permissions to access and use the application. | Now that you have set up a Site/Digital Experience, you will need to grant the "guest user" (default user assigned to people interacting with the site) with the correct permissions to access and use the application. | ||
... | [TODO] | ||
=== Configure a Custom Domain for Your Experience Cloud Site === | |||
You can use your own domain name with Sites/Digital Experiences so you can brand the experience to your liking. This means you can change the URL of publicly posted documents from say https://my.domain.salesforce.com/documents to https://yourwebsite.com/documents. Follow the instructions below or refer to the documentation provided by Salesforce. | |||
# From Setup, enter <kbd>Domains</kbd> in the Quick Find box, then select Domains. | |||
# Click Add a Domain. | |||
# Enter the domain name. | |||
# Choose the HTTPS domain configuration option you want to serve this domain with. Optionally, specify a CNAME value if you’re using a non-Salesforce provider to serve your domain. NOTE In Professional Edition orgs with Pardot, you must choose Salesforce serves the domain over HTTPS using a Salesforce content delivery network (CDN) partner. | |||
# To avoid vulnerabilities during HTTP redirects and to have supported web browsers always use secure HTTPS connections for your domain, select Allow HSTS preloading registration. This setting adds the <samp>preload</samp> directive to the HSTS header. After you enable this setting, you must submit your domain at <nowiki>https://hstspreload.org</nowiki>. NOTE This setting applies only to domains that are eligible for HSTS preloading. Domain names can consist of a public suffix plus one additional label, For example, <samp>example.com</samp> and <samp>example.co.uk</samp> are eligible, but <samp>www.example.com</samp>, <samp>www.example.co.uk</samp>, and <samp>sub.example.com</samp> aren’t eligible. | |||
# Add a certificate if you have already set up a CA-signed certificate that supports this domain. | |||
# Click Save. To add another domain, click Save & New. | |||
If you plan to host more than one Experience Cloud site on a domain, you’ll need to set up custom URLs for each site. Custom URLs are the way to uniquely distinguish the sites within that domain. From Setup, enter <kbd>Custom URLs</kbd> in the <samp>Quick Find</samp> box, then select Custom URLs. | |||
Before pointing your domain name’s CNAME to a new target name, ensure that the target name exists in the DNS by using <code>dig</code> or <code>nslookup</code>. The target of your CNAME depends on when you create your domain name. | |||
* To use HTTPS for domain names added before the Summer ’13 release, adjust your CNAME to point to the FQDN followed by <samp>.live.siteforce.com</samp> instead of to the org’s <samp>force.com</samp> subdomain. For example, if your pre-Summer ’13 domain is <samp>www.example.com</samp>, its CNAME target is <samp>www.example.com.live.siteforce.com</samp> instead of <samp>example.force.com</samp>. | |||
* Domain names added in Summer ’13 or earlier don’t have the 18-character org ID in the CNAME target. | |||
* Domain names added in Summer ’13 or later point to the location for setting up HTTPS in a custom domain. | |||
* Domain names added in Winter ’14 or later use a CNAME that points to the FQDN followed by your org’s 18-character ID and <samp>.live.siteforce.com</samp>. For example, if your domain name is <samp>www.example.com</samp> and your 18-character org ID is <samp>00dxx0000001ggxeay</samp>, its CNAME target is <samp>www.example.com.00dxx0000001ggxeay.live.siteforce.com</samp>. | |||
== Upgrading == | == Upgrading == | ||
We regularly push upgrades to our customers, however if you wish to manually upgrade your instance to a specific version, follow the "Install from Link" instructions. | We regularly push upgrades to our customers, however if you wish to manually upgrade your instance to a specific version, follow the "Install from Link" instructions. | ||