The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Restricting Shopper API traffic to Managed Runtime with eCDN rules (opens in a new tab)

You will learn how to lock SCAPI traffic to Managed Runtime with the SCAPI Identity Header, allow other integrations, harden SLAS, and rate limit AI crawlers using eCDN fields and rule expressions.

  1. Enable SCAPI Request Identification per instance
  2. Add a block rule for the instance's path
  3. Place the rule after the Salesforce allow rule
  4. Start in Log mode, then switch to Block
How to restrict Shopper API traffic to Managed Runtime, rolled out in stages

Bots increasingly call the B2C Commerce API directly, bypassing storefronts, and AI crawlers and shopping agents add search and LLM costs and skew analytics. The October 2026 release lets you manage the SCAPI zone in Business Manager and the CDN API, accept Shopper API traffic only from Managed Runtime through the new SCAPI Identity Header, and identify AI traffic on any eCDN zone with verified-bot fields. The SCAPI zone is provisioned automatically and shared across Development, Staging and Production, managed from Production. Some controls such as WAF managed rulesets, mTLS, TLS 1.3 settings and HSTS are not available.

To restrict traffic, enable the Managed Runtime SCAPI Request Identification feature per instance, then add a firewall rule that blocks Shopper API paths for that instance’s org-specific path segment, placed after the locked Salesforce allow rule. Start with Log, then switch to Block. Other integrations such as a custom BFF can be allowed with their own rules carrying a separate shared secret header that must stay server-side. For SLAS, Strict Client Auth requires a client secret header on login and authorize requests, though Composable Storefront and Storefront Next do not send it yet, so it should be enabled only for private clients called from your own server code. SLAS also throttles refresh-token exchanges to 3 per 60 seconds.

For AI traffic, the Known Bot and Verified Bot Category fields sort verified bots into 17 categories. The post recommends rate limiting AI Crawler and AI Search traffic on expensive endpoints such as product search rather than blocking it, with thresholds tuned from logs and Log mode run first. Spoofed or unverified automation needs behavioral detection from a bot management partner or Bot Management in front of eCDN.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

B2C Commerce release 26.9 introduces edge credential detection and SFRA password warnings (opens in a new tab)

Readers will learn how to configure Cloudflare firewall and rate limiting rules in B2C Commerce to block leaked credentials, and how to implement server-side header checks in SFRA to prompt users to rotate breached passwords.

The September 2026 update to B2C Commerce adds built-in credential stuffing protection through its eCDN layer without requiring additional entitlements. Four new detection fields evaluate login attempts against known breach data, allowing administrators to create custom firewall and rate limiting rules at the network edge.

The article provides exact rule syntax examples to throttle malicious traffic while preserving verified search crawlers. It explains how to use managed challenges for password leaks and emphasizes separating counting expressions from rule expressions to avoid penalizing legitimate bot activity.

For storefront implementations, the piece details how to read a server-side request header added by Cloudflare after a successful login. A working SFRA code example demonstrates how to map header values to user-facing warning messages and direct shoppers to a password reset flow, deliberately avoiding failed login responses to prevent information leakage to attackers.

Finally, the author outlines monitoring strategies using Security Analytics in Business Manager and eCDN Logpush exports, recommending these detections as a baseline before layering in broader bot mitigation controls.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?