[MAIN] STERICMS-959 — OneTrust cookie banner reappears after Accept/Reject on non-production hosts

[Mao8a]

Summary

STERICMS-959 — OneTrust cookie banner reappears after Accept/Reject on non-production hosts
https://herodigital.atlassian.net/browse/STERICMS-959

Root cause

scripts/otconfing.js defaulted any unmatched host to the production OneTrust domain script (94a9f9f7-2ccd-4f46-b1a1-d11d479ed08c), which OneTrust authorizes only for shredit.com. Preview (*.aem.page), live mirror (*.aem.live), and localhost fell through to that production ID, so consent could not be recorded and the banner reappeared after every Accept/Reject. Only reproduces from consent-required regions (e.g. Bogotá/EU), not US regions.

Fix

Rewrote getOneTrustConfig() in scripts/otconfing.js to return the production config only for the production domains and the -test config as the fail-safe default for every other host:

export default function getOneTrustConfig(pageUrl) {
  if (/^https?:\/\/(www\.)?shredit\.com(\/|$)/.test(pageUrl)) return PROD_CONFIG;
  return TEST_CONFIG;
}

TEST_CONFIG uses domain script 94a9f9f7-2ccd-4f46-b1a1-d11d479ed08c-test. No change to shredit.com / www.shredit.com, no new dependencies, no build step, aem.js untouched.

Test URLs

OneTrust only renders the banner from a consent-required region (e.g. Bogotá/EU) — not from US regions.

Before:

• https://main--shred-it--stericycle.aem.page/en-us

After:

• https://bugfix-stericms-959-onetrust--shred-it--stericycle.aem.page/en-us

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run all PSI checks
• Re-run failed PSI checks
• Re-sync branch

Commits

• f9ea318 ✅ (latest)

[aem-code-sync]

	Page	Scores	Audits	Google
📱	/en-us
🖥️	/en-us