Custom HTTPS Domains Supported for Communities

You can now set up a custom domain with HTTPS so that your community URLs reflect your company brand.

As of Winter '15, new Salesforce Communities require secure connections by default. Existing Salesforce Communities will continue to not require HTTPS for all connections by default. Authenticated requests in a Salesforce Community continue to require secure connections when the organization requires secure connections in the session settings.

Note

Note

Before you switch the CNAME of your domain name to point to a new target name, ensure that the new target name exists in the DNS by using dig or nslookup. When you created your domain names affects the target of your CNAME:
  • Domain names that were added before Summer ‘13, typically need to have their CNAME adjusted to point to the fully qualified domain followed by .live.siteforce.com instead of to the organization’s force.com sub-domain. For example, if your pre-Summer ‘13 domain is www.example.com, then the target of its CNAME will need to be www.example.com.live.siteforce.com instead of example.force.com before HTTPS will work.
  • Domain names that were added in or before Summer ‘13, don’t have the 18-character organization ID in the CNAME target.
  • Domain names that were added in or after Summer ‘13, already point to the proper place for setting up HTTPS in a custom domain.
  • Domain names that were added in or after Winter ‘14, use a CNAME that points to the fully qualified domain followed by your organization’s 18-character ID and .live.siteforce.com. For example, if your domain name is www.example.com and your 18-character organization ID is 00dxx0000001ggxeay, then the target of its CNAME will need to be www.example.com.00dxx0000001ggxeay.live.siteforce.com.