Skip to content

Dashboard cutover — legacy allowlist on the dash listener

Status (as of 2026-11-05): specification and Terraform written, nothing applied. The routing flip itself is CH-359; this page and the infra change behind it (CH-357) make sure the flip does not break anything Laravel still serves.

At the cutover, the dashboard hostname (dash.cookiehub.com, dash.stage.cookiehub.net on stage) stops being served by the Laravel dashboard and is served by the React dashboard (core-portal) instead. Laravel exposes more than the dashboard's pages: payment gateways, crawlers, partner platforms, SSO providers and customer sites all call URLs on that hostname. Every URL that nothing else serves yet must keep reaching Laravel. This page lists them, says in what order the load balancer decides, and says what to do when one is missed.

Required access

  • AWS: read access to the public ALB and its listener rules in the target account (stage 258618559895, prod 759286286879). Changing rules by hand needs elasticloadbalancing:CreateRule/DeleteRule on the listener. Terraform changes are applied by Ástþór, from an Infrastructure & Security issue and a reviewed pull request.
  • Secrets / SSM: none.
  • VPN / SSM tunnel: none. Everything here is public HTTPS.

How the routing works

The public ALB has one HTTPS listener. Its listener-level default action is a fixed 404 Not Found, and it is not what this page calls "the default". The dashboard's default is a host rule: every request for the dashboard hostname that no other rule claimed. On stage this is dash_https (priority 1000, environments/stage/eu-central-1/dash.tf) and it forwards to the Laravel target group.

priority   rule                                         forwards to
--------   -------------------------------------------  ---------------------------
10         dsar-api: host api.* + /dsar/*               dsar-api              (other host)
30         core-api: host core-api.*                    core-api              (other host)
100-120    stage only: /client/v3 docs block, /client/v3/*, /client-api/v2 bridges  core-api
130-199    reserved: dashboard-host rules that must beat the allowlist (CH-1215: public DSAR paths -> dsar-api)
200-299    THE ALLOWLIST (this page): one rule per group, host + paths  Laravel
300-999    free: hot-fix rules
1000       dashboard catch-all, host only               Laravel today, React after CH-359
(listener default)                                      fixed 404

The lower number wins. The allowlist sits below anything that must override it (the stage /client-api/v2 bridges to core-api, and the DSAR path rules CH-1215 adds) and above the catch-all. Because the allowlist forwards to the same Laravel target group the catch-all uses today, adding it changes no routing. It only starts to matter when the catch-all moves.

The change at the flip (CH-359, not CH-357)

One edit per environment: the catch-all's target_group_arn changes from the Laravel target group to the React dashboard's target group. Nothing in the allowlist changes. Rolling back is the same edit in reverse.

What an ALB rule can express

  • path_pattern takes * (any run of characters, / included) and ? (one character). No regular expressions, no character classes. The query string is not matched. Matching is case-sensitive.
  • A path pattern is at most 128 characters. A rule has at most 5 condition values; this page reads that as per rule, not per condition, so with the host condition taking one value each rule holds at most 4 path patterns. A listener holds at most 100 rules (the public listener already carries the rules of every service, so the allowlist is kept to a handful of grouped rules rather than one per path).
  • A path pattern cannot say "POST only". Methods are listed in the tables below for information; the allowlist matches by path. (An http_request_method condition exists and costs a condition value; it is not used.)
  • A bare prefix needs two patterns when the prefix itself is a route: /cmp-api and /cmp-api/*, /cha and /cha/*. /pp and /pp/* likewise (an exact /pp plus /pp/{id}, without matching /ppxyz).
  • Group paths under a prefix wherever the whole prefix belongs to Laravel (/api/*, /wix-api/*). Do not enumerate single routes inside one: that is what runs into the 4-value limit.

Inventory

Source: the routes core declares, routes/web.php plus every route file mounted in RouteServiceProvider (api, client-api/v2, wp-api, api/v3, cmp-api, api/widget/v1, wix-api, webflow-api, shopify-api, cha), and the files in core's public/ directory (served by the web server, not by a route). The routes are the ones in the committed snapshot in core-portal (tests/sweep/legacy-routes.generated.ts, 176 web routes and 11 mounted route files, taken from core at 3da59c3). Core's routes and public/ directory have not changed between that commit and main on 2026-11-05. The decisions are the dispositions in tests/sweep/legacy-dispositions.ts; legacy-routes.test.ts fails if a route has neither a React route nor a disposition, which is what keeps the allowlist honest.

Outcome after the flip Web routes Mounted route files
Served by the React dashboard (incl. 17 redirects) 130 0
Stays on Laravel (the allowlist) 17 10
Retired: a 404 by design, nobody outside legacy's own pages calls it 29 1

Stays on Laravel (the allowlist)

"External" is Yes where a third party, a sent email or a file already on customer sites holds the URL, so the URL cannot move without that party changing something. The group column is the listener rule in the Terraform module modules/dash/legacy-allowlist and its priority; the exit issue is the one that removes the entry.

Path pattern Methods Owner after the flip Why it stays External Rule (priority) Exit
/dsar/verify/{token} GET, POST Laravel; dsar-api ported Public data-subject page in DSAR emails. dsar-api serves the same path but is not routed yet Yes: links in sent emails dsar_public (200) CH-1384, CH-1215
/dsar/form/{slug} GET Laravel; dsar-api ported Public hosted request form, linked from customer sites Yes: links on customer sites dsar_public (200) CH-1384, CH-1215
/dsar/request/{uuid} and /download/{id}, /resend/{audience}, /message, /appeal GET, POST Laravel; dsar-api ported Public request status page and its actions, linked from DSAR emails Yes: links in sent emails dsar_public (200) CH-1384, CH-1215
/api/v1/dsar/init, /api/v1/dsar/submit (+ OPTIONS) GET, POST, OPTIONS Laravel; dsar-api ported The DSAR widget API; the widget on customer sites hardcodes the dashboard host Yes: embedded in customer sites dsar_public (200) CH-1384, CH-1215
/pp, /pp/{id} POST Laravel Teya/Borgun 3-D Secure return; the term URL sent with each card transaction points here (stage: https://dash.stage.cookiehub.net/pp) Yes: gateway posts the cardholder's browser back gateway_callbacks (210) CH-589
/paypal/ipn POST Laravel PayPal instant payment notification Yes: registered with PayPal gateway_callbacks (210) CH-1427
/wise/deposit POST Laravel Wise deposit notification Yes: registered with Wise gateway_callbacks (210) CH-1428
/checker/callback POST Laravel Atrax scan-result callback (Atrax is configured with the dashboard URL) Yes: Atrax's configuration (core_app_url) crawler_callbacks (220) CH-1322
/implementation/callback POST Laravel Atrax installation-check callback Yes: same crawler_callbacks (220) CH-1322
/wp-api/*: auth, domain, domain/{code} GET, POST Laravel The WordPress plugin; installed plugins call it Yes: baked into installed plugins platform_apps (230) CH-1431
/wix-api/*: webhook, oauth/install, detail/{id}[/settings], instance/{detail,settings,template,scan} GET, POST, OPTIONS Laravel The Wix app backend: webhook, OAuth install, server-to-server and browser calls with CORS Yes: registered with Wix platform_apps (230) CH-1434
/webflow-api/*: domain-check, lookup-code, set-origin, provision GET, POST Laravel The Webflow app, server to server Yes: registered with Webflow platform_apps (230) CH-1435
/shopify-api/*: provision, uninstall/{shop}, detail/{shop}[/settings,/template,/scan,/tier] GET, POST Laravel The Shopify app backend, server to server Yes: registered with Shopify platform_apps (230) CH-1436
/api/*: token, user, account/*, domain/*, cookie, access-key, totp/* ... (about 85 routes) GET, POST, PATCH, DELETE Laravel The token-authenticated v1 API. External callers are not inventoried Probably: customer scripts (unknown callers) legacy_api (240) CH-1430
/api/mailchimp/webhook, /api/userlist/subscribe, /api/userlist/unsubscribe POST Laravel Webhooks from Mailchimp and Userlist (inside /api/*) Yes: registered with the vendors legacy_api (240) CH-1430
/api/_log/domain, /api/_log/report POST Laravel Log endpoints (inside /api/*) Unknown callers legacy_api (240) CH-1430
/api/widget/v1/releases POST Laravel The widget repository's release job uploads a release here (inside /api/*) Yes: a CI workflow legacy_api (240) CH-1433
/api/v3/* any Laravel (answers 403) Pre-core-api routes, all behind devmodeonly, which answers 403 in production. Caught by /api/*; left as is No legacy_api (240) none; goes with Laravel
/client-api/v2/* (about 60 routes) GET, POST, PATCH, DELETE Laravel (stage: parts on core-api) The customer API v2. core-api's /client/v3 is its successor Yes: customers' integrations legacy_api (240) CH-1430
/cmp-api, /cmp-api/* GET, POST Laravel Google CMP provisioning API Yes: registered with Google legacy_api (240) CH-1432
/scanner-ip, /scanner-ip/json GET Laravel The crawler's published IP list; customers allow-list it in their firewalls from the docs Yes: linked from the docs public_assets (250) CH-1429
/image-handler/{filename} GET Laravel Serves reseller logos uploaded through legacy Yes: logo URLs already stored and mailed public_assets (250) CH-251
/images/* (file public/images/) GET Laravel (static file) Every transactional email's layout loads /images/cookiehub-white.png from the dashboard host; invoice PDFs load /images/cookiehub.png Yes: images in sent emails, cannot be recalled public_assets (250) none yet (gap 1)
/dpa/* (file public/dpa/CookieHub-DPA-2023.pdf) GET Laravel (static file) The DPA PDF; may be linked from contracts and the website Possibly static_files (260) none yet (gap 1)
/gtm-template/* (files in public/gtm-template/) GET Laravel (static file) The GTM template files; may be linked from GTM documentation Possibly static_files (260) none yet (gap 1)
/robots.txt GET Laravel (static file) The React dashboard serves no robots.txt; this one stays until it does Crawlers static_files (260) none yet (gap 1)
/cha, /cha/* GET, POST Laravel The internal admin; a separate admin app replaces it No (staff only) internal_admin (270) IS-36

Served by the React dashboard

These need no rule: the React app serves the same path (app/routes.ts), or redirects from it (app/routes/legacy-redirect/targets.ts). Several of them are externally registered, so they have to keep answering at exactly the legacy path; they are listed here because the allowlist is the wrong place for them, and the flip checklist must verify them.

Path Methods Why it matters at the flip Externally registered
/saml/acs POST SAML assertion consumer service, registered at every customer IdP Yes. Needs an IdP round trip before the flip (CH-320)
/saml/metadata/{accountId}, /saml/login GET SP metadata URL and login start, registered at customer IdPs Yes
/sso/callback/{provider}, /login/sso/{key}, /sso/register GET, POST OIDC redirect URI and SSO start, registered at customer IdPs Yes. Same IdP round trip
/verify/{id}, /reset-password/{id}, /magic-link/{id}, /register/invitation, /invitation/accept/{id}, /invitation/deny/{id}, /unsubscribe/* GET, POST Tokenized links in sent emails Yes: in sent emails
/terms GET A redirect to the marketing site's terms, as legacy Yes: old links
/login, /logout, /register*, /lost-password, /, /domain/*, /account/*, /billing/*, /reseller/*, /affiliate/*, /overview/*, /profile, /contact, /access-key, /cookie/report, /dsar (the queue), /dsar/manage/{uuid}, /dsar/systems, /dsar/settings, /dsar/new GET, POST The dashboard's own pages (every other route) No
/oauth/consent/{uid}, /account/ai-assistants, /dsar/publish, /dsar/counts GET, POST New URLs with no legacy equivalent No

core-api serves the dashboard's data on its own hostname (/dash/v1), and its OAuth and MCP endpoints live there too (/oauth/*, the RFC 8414 well-known document). None of that is on the dashboard hostname, so none of it is in play here. dsar-api serves the DSAR screens' data the same way; its public pages are the DSAR rows of the allowlist above.

Retired: a 404 on the React dashboard, on purpose

Nobody outside legacy's own pages calls these, so after the flip they 404.

Path Methods Why
/stats519, /mailtest1 GET Internal pages with obscured names; nothing links them
/account/vendor-tcf, /account/vendor-tcf/list GET, POST Orphaned page; nothing links it
/billing/transaction/{id}/creditpdf, /billing/adjust GET, POST No customer screen links them (decisions D4 and plan section 3.6)
/account/user/{id}/dsar POST A legacy form post; the roster's switch calls core-api now
/dsar/export, /dsar/hosted-form/{domainId}, /dsar/manage/{uuid}/{update,sync,delete,assign,message,consent-history,verification,appeal/...}, /dsar/manage/reopen/{uuid}, /dsar/manage/service-toggle/{pivotId}, /dsar/manage/{uuid}/audit.csv, /dsar/manage/{uuid}/message/{id}/file, /dsar/systems/{id}/delete, /dsar/settings/{test,clear}, /dsar/{uuid}/upload-staged/{serviceId}, /dsar/remove-staged/{id}, /dsar/download-staged/{id} GET, POST, DELETE The legacy DSAR management pages' own endpoints; the React screens call dsar-api directly (the file endpoints follow in CH-1335)
routes/core-api.php (/api/v3/*) any Behind devmodeonly, 403 in production; the allowlist's /api/* leaves it as Laravel answers it today
Static files that only legacy's Blade pages load: /js/*, /css/*, /fonts/*, /vendor/*, /c2/*, /cdn/*, /client/*, /dev/*, /dsar_widget.htm GET Assumed unreferenced. This is an assumption, not a finding: check the access logs before the flip (gap 2)
/preview/*, /_mail/images/logo.png GET Not retired: the React dashboard ships its own public/preview/* and public/_mail/images/logo.png and serves them. Laravel's copies are not allowlisted

Gaps: paths nobody serves after the flip

  1. Static files with no owner. legacy-dispositions.ts covers routes, not the web server's public/ directory. /images/* is certain to matter (every email layout loads it from the dashboard host, and sent emails cannot be recalled); /dpa/*, /gtm-template/* and /robots.txt are probable. The allowlist keeps all four on Laravel, but they have no exit issue: either serve them from the React app or a CDN and move the URLs, or accept that Laravel keeps a static origin. Needs an owner and an issue.
  2. Static files assumed dead. The last row of the retired table has not been checked against traffic. Pull a week of dashboard access logs for /js, /css, /fonts, /vendor, /c2, /cdn, /client, /dev and /dsar_widget.htm before the flip.
  3. Unknown callers of /api/* and /client-api/v2/*. They stay on Laravel, so nothing breaks at the flip, but nobody has inventoried them, which is what blocks CH-1430's exit.
  4. IdP round trips. SAML and OIDC paths are served by the React app, not allowlisted. Their sweep rows are human checks needing an IdP test account, and they have not been run. A broken ACS locks out every SSO customer.
  5. Prod is not on the ALB at all. See the next section.

Production differs from stage

Stage's dashboard hostname is already on the public ALB, with the Laravel target group and the catch-all. Prod's is not. dash.cookiehub.com is on Cloudflare and goes straight to the Laravel server cs150p, which is not managed by Terraform (environments/prod/eu-central-1/dash.tf). Prod also has no React dashboard yet: no core-portal service, repository or target group.

The infra change therefore adds to prod a Laravel target group (attached to cs150p by instance id) and the same allowlist rules, dormant: no DNS record sends the hostname to this ALB, and the ALB certificate (*.cookiehub.net) does not cover it. Before the prod flip (CH-359) these must exist:

  • the React dashboard in prod (the modules/dash/portal module, and its image released), with the dash host catch-all at priority 1000 forwarding to it;
  • an ACM certificate for dash.cookiehub.com on the HTTPS listener (validated in Cloudflare DNS);
  • a security group rule letting the ALB reach cs150p on the target port, and a confirmed origin port and health-check path for the Laravel target group (the repo does not record them; the change assumes port 80 and /, as stage does);
  • the Cloudflare change that moves the hostname to this ALB. Behind Cloudflare Laravel sees Cloudflare's addresses; behind the ALB it sees the ALB's, so check client-IP handling and any Cloudflare page rules or WAF rules that the allowlist paths currently pass through;
  • the prod copies of the stage-only rules at 100-120, only if prod needs them: /client/v3/* and the /client-api/v2 bridges to core-api exist on stage's dashboard host because stage's dashboard calls them there. Laravel does not serve /client/v3, so nothing is lost on prod by leaving them out.

Prod core-api and dsar-api run with desired_count = 0 today, so the DSAR paths stay on Laravel at the flip unless CH-1215 has landed first.

Doing the flip safely

  1. Apply the allowlist (CH-357). Confirm each group's rule exists on the listener at the priorities above.
  2. Before changing the catch-all, request one URL per group from the ALB with the dashboard Host header and confirm Laravel answers (examples: GET /scanner-ip/json returns the IP list; GET /images/cookiehub-white.png returns an image; GET /cha returns the admin's page or its login redirect; POST /paypal/ipn with an empty body gets Laravel's answer, not a not-found page).
  3. Run the IdP round trips (gap 4) against the React app.
  4. Flip the catch-all (CH-359). Watch the React target group's 4xx count and its request log for the first hour.

How a missed path shows up

A path that Laravel served and neither the allowlist nor the React app does is answered by the React dashboard's not-found page, HTTP 404, from the moment the catch-all moves. Nothing else in the stack notices:

  • A person sees the dashboard's "page not found" page at a URL that used to work (a link in an old email, a bookmark, a customer's docs).
  • A machine caller (a webhook, a plugin, a script) sees a 404 and, usually, retries or reports a failed delivery in its own console: PayPal and Wise in their notification histories, Atrax as a scan that never completes, partner platforms as an install or provisioning error. The first sign on our side is often an absence: payments that do not post, scans stuck in progress.
  • On the load balancer, the React target group's HTTPCode_Target_4XX_Count rises. The React app's request log names the path. If ALB access logs are enabled for the public ALB they show it with the user agent, which usually identifies the caller.

Hot-fix: add a rule

  1. Find the path and method in the log, and check it is really Laravel's (routes/*.php in core, or a file in public/).
  2. Create a listener rule at a free priority in 300-999 on the public HTTPS listener: conditions host = the dashboard hostname and path = the path (or its prefix with *), action forward to the Laravel target group. In an incident this is done by hand in the console or CLI; the infra convention is that the same change goes into Terraform the same working session. Because the rule sits above 1000 it wins over the catch-all immediately, with no deploy.
    # The public ALB's HTTPS listener ARN: from the load balancer ARN ...
    aws elbv2 describe-listeners --load-balancer-arn <public-alb-arn> \
      --query "Listeners[?Port==\`443\`].ListenerArn" --output text
    # ... or from Terraform: aws_lb_listener.public_https (stage and prod roots).
    # Pick a priority nobody holds: aws elbv2 describe-rules --listener-arn <listener-arn>
    
    aws elbv2 create-rule \
      --listener-arn <listener-arn> \
      --priority 310 \
      --conditions \
        '[{"Field":"host-header","HostHeaderConfig":{"Values":["dash.cookiehub.com"]}},
          {"Field":"path-pattern","PathPatternConfig":{"Values":["/missed/path/*"]}}]' \
      --actions Type=forward,TargetGroupArn=<laravel-target-group-arn>
    

Codify it the same session: add the path to the right group in modules/dash/legacy-allowlist/main.tf (step 3), so the next apply owns it. 3. Open the infra pull request that puts the path in the right group of modules/dash/legacy-allowlist/main.tf (or a new group at a free priority in 200-299), delete the hand-made rule once that is applied, and record the path on the CH-357 issue so the hand-off list below stays complete. 4. Tell the core team: the path is now part of what Laravel must keep serving.

Hand-off to core's post-flip cleanup

The allowlist is the list of what stops core from being deleted. Each group has an exit condition and an owner issue, and nothing on it is permanent:

Group (rule priority) Exit Owner issue(s)
dsar_public (200) Port: dsar-api already serves these paths. CH-1215 adds the dashboard-host rules (priorities 130-199) pointing at dsar-api, after which delete the group CH-1384, CH-1215
gateway_callbacks (210) Port to core-api; the gateway-side URLs change with it CH-589 (Teya/Borgun), CH-1427 (PayPal), CH-1428 (Wise)
crawler_callbacks (220) Port to core-api; Atrax's callback URL is configuration CH-1322
platform_apps (230) Port each backend; the URLs are registered with the platforms or inside installed plugins, so each port keeps the old path working or needs the platform's cooperation CH-1431 (WordPress), CH-1434 (Wix), CH-1435 (Webflow), CH-1436 (Shopify)
legacy_api (240) Port /api and /client-api/v2 to core-api (/client/v3 is the successor), inventory the callers first; port the Google CMP, Mailchimp and widget-release endpoints CH-1430, CH-1432, CH-1433
public_assets (250) Port /scanner-ip and /image-handler; move the email images (gap 1) CH-1429, CH-251, none for /images/*
static_files (260) Decide an owner (gap 1) none yet
internal_admin (270) Retire when the separate admin app replaces /cha IS-36

When a group's exit lands, the cleanup removes its paths from modules/dash/legacy-allowlist/main.tf, and the rule disappears. When the module's group list is empty, nothing is left that needs Laravel on this hostname: the Laravel target group, its server, and the module can be removed.

To re-derive the list from code rather than from this page: allowlistedPaths() in core-portal's tests/sweep/legacy-dispositions.ts returns the route-derived entries. Re-run scripts/snapshot-legacy-routes.mjs in core-portal when core's routes change; the test then names every new URL that needs a decision. Static files in public/ are not covered by that test and must be re-read by hand.