top of page
  • Writer's pictureshannan

Salesforce My Domain Change Pre-Deployment Checklist


Example Pre-Deployment Checklist

  • Allowlists—Update your allowlists for any new domains.

  • Custom Visualforce pages or custom apps—Replace references to the org’s instance URL with relative URLs and dynamically generated hostnames. Note any URLs that require a hard-coded reference.

  • Einstein Bots—Identify the web pages and sites that use your bots. For each chatbot, review the Permitted Domains field in the chat deployment settings.

  • External software that accesses your Salesforce org—Verify that the external software that uses your Salesforce URLs, including site URLs, can process redirections. If the software can’t process those redirects, work with the software owner to get that redirection functionality in place or plan to update your use of the software with your new URLs after you deploy the change.

  • Firewalls and Proxy Servers—Update trust settings that filter by hostname. Include all applicable URL formats for your new configuration.

  • Identity providers on your Salesforce login page—Note any authentication options available to your users.

  • Installed Packages from AppExchange—To get the latest fixes, potentially including fixes for enhanced domains, install the latest version of each package. Note the package providers so that you can report any issues detected.

If the change to your My Domain updates your My Domain login URL, complete these tasks.

  • Authentication options such as single sign-on (SSO), authentication providers, and named credentials—Plan to update authentication. Document your existing settings for your rollback plan.

  • Knowledge articles served on your *.my.salesforce.com URL—Search for hard-coded references to the knowledge article URLs.

  • Preserve login access for your admins and end users.

If the change to your My Domain changes your Experience Cloud sites login URL, complete this task.

  • A Mobile Publisher for Experience Cloud app that uses your Experience Cloud site login URL—Before you deploy enhanced domains in production, upgrade to Mobile Publisher version 10.0 or later.

If the change to your My Domain changes your Experience Cloud sites or Salesforce Sites URL, complete these tasks.

  • Authentication options such as single sign-on (SSO), authentication providers, and named credentials—Plan to update authentication. Document your existing settings for your rollback plan.

  • Knowledge articles served on your Experience Cloud site URL—Search for hard-coded references to the knowledge article URLs.

  • Identity providers on your site login page—Note any authentication options available to your users.

  • Multi-factor authentication (MFA) for your site—Preserve login access for your admins and end users.

If you have Experience Cloud sites or Salesforce Sites and the My Domain change includes deploying enhanced domains, complete these tasks.

  • External integrations—Work with third parties that currently integrate with your *.force.com site URL to ensure that they support Server Name Indication (SNI).

  • IP restrictions are configured in Salesforce with only IPv4 addresses—Update your IP allowlists or restrictions to allow IPv6 source addresses for authorized users. Review and update the login IP range restrictions for the relevant profiles, including the site’s guest user profile.

  • Trusted domains for inline frames—Review and update the list of trusted domains for clickjack protection. Ensure that *.my.salesforce.com is trusted.

  • Visualforce pages with embedded Lightning components—For each Experience Cloud site with Visualforce pages that include embedded Lightning components, update the Security & Privacy settings, and add your Lightning Components URL to the Trusted Sites for Scripts.



Comentarios


bottom of page