Add a SSL Certificate to an eCDN Zone and Configure DNS Mapping

Add SSL certificates to your hostnames for Zones, and map your origin endpoints.

When mapping endpoints, keep the following in mind:

  • The DNS RFC does not support pointing root domains directly to B2C Commerce. When directing root domains to the eCDN CNAME alias, you must use an external service to redirect from the root domain to the subdomain.
  • When setting up redirects, make sure to set them up for both HTTP and HTTPS.
  • To permanently serve traffic from the root domain (youcompany.com) instead of a subdomain (www.yourcompany.com), use a DNS-level solution to direct root domains to the eCDN CNAME alias.

To add SSL certificates to your hostnames and map DNS values from B2C Commerce to your DNS provider account:

  1. Select Administration > Sites > Embedded CDN Settings.
  2. Click Certificates or Settings for the zone that you’re adding a certificate to.
  3. On the Crypto tab, select the zone from the list.
  4. Click Add Certificate.
  5. Enter the SSL certificate and private key information from your certificate provider.
  6. Select the hostname to which you want to assign the SSL certificate.
  7. Click Upload Certificate.
  8. Copy the displayed verification text into your own DNS portal.
  9. To check the status of hostname validation, click Verify HostName . This verification can take up to six hours.
  10. After the hostname is active, create a CNAME record that points traffic, by SSL for SaaS V2, to the new zone.
  11. Configure DNS mapping for the zone:
    1. Log into your DNS provider account.
    2. Search for your zone and select it from the list.
    3. On the DNS tab, locate the hostname that you want to map.
    4. Replace all text after β€œis an alias of” with the DNS CNAME from Business Manager.
    5. In the Status column, click the cloud until it shows a gray cloud with the tooltip β€œDNS Only”.
    Note: If you already have the same root domain with your DNS provider in a separate account, it is required to point the DNS to the new zone and not the standard or root zone. The purpose is to prove intent that you want traffic to come to the new zone rather than the standard or root zone.