As announced in the 24.7 release notes, B2C Commerce now prevents traffic that
doesn’t originate from Commerce Cloud eCDN from accessing hyphenated demandware.net host
names, such as
staging-xxx.demandware.net, to the Open
Commerce API (OCAPI) or Storefront. Traffic through demandware.net doesn’t have eCDN controls in place, posing a potential risk to
your data security. Origin Shielding for staging makes sure that all external traffic goes
through the eCDN security layers before reaching your environment. The introduction of
Origin Shielding for staging impacts Commerce Cloud customers who have implementations that
involve direct calls to POD IPs.
When: This change takes effect on October 7, 2024.
How: To prepare for this upcoming change:
- Evaluate your implementations for calls made to OCAPI or Storefront using direct POD
IPs, dot-form host names, or hyphenated host names for
demandware.net, for example,staging.xxx.demandware.netorstaging-xxx.demandware.net. - Update services or applications to use the vanity host name and route traffic through eCDN.
You can create a proxy zone on staging instances through Business Manager and configure a custom host name with an automatically renewing eCDN managed certificate for added protection.
For further assistance, contact your Customer Service Manager.