Skip to content

Enforce provider opt-outs and legacy EID expiry on Fastly and Axum - #1626

Open
prk-Jr wants to merge 6 commits into
feat/1574-axum-shared-identityfrom
fix/1555-provider-eid-opt-outs
Open

prk-Jr wants to merge 6 commits into
feat/1574-axum-shared-identityfrom
fix/1555-provider-eid-opt-outs

Conversation

@prk-Jr

@prk-Jr prk-Jr commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Enforce remembered provider opt-outs on client cookie/body EIDs across Fastly and Axum direct, initial-page and page-bids auctions, preserving unrelated IDs and opt-back-in.
  • Immediately expire legacy browser single-UID records while an enabled provider owns their emitted source. Preserve live provider UID expiry and no-provider behavior.
  • Refresh onto Run Axum identity through the shared application #1646's shared identity application and prepared native record startup. Do not restore removed adapter-local identity/store code.

Stack and refresh

Base: feat/1574-axum-shared-identity (#1646), head c054ece709457dd4420aac27ccbb40c57e8c1cb0. This includes #1566 (240149789), and through #1646 this PR depends on #1641, #1635, #1613 and #1637; #1624 supplies SharedID write-back earlier in the identity stack.

Signed merge d72c8bb37f4133bc81074270feb2cc28a10c88f3 directly merges #1646 into the existing #1626 head ee7a11031. No separate #1566 merge, rebase or force-push. The new merge is locally verified and GitHub Verified. No dependency branch was modified.

Whenever #1646 changes during review, merge its new head into this branch and revalidate the affected behavior before readiness.

Merge resolutions

Conflict Resolution
Cargo.lock Retain #1646's dependency graph.
Axum Cargo.toml Retain current prepared-startup and provider dependencies.
Axum app.rs Retain shared IdentityApp lifecycle and prepared record binding.
Axum lib.rs Keep removed adapter-local identity/store modules absent.
Axum middleware.rs Retain managed geo and current response finalization.
Fastly app.rs Retain shared lifecycle delegation; discard obsolete policy-only graph machinery.
CLI checked_app_config.rs Retain current supported-adapter validation.
Core auction/endpoints.rs Add matching-row remembered opt-outs to current vendor/cookie checks; preserve SharedID filtering and body ingestion.
Core ec/eids.rs Combine remembered opt-outs and immediate legacy expiry with current canonical SharedID output.
Core ec/identify.rs Apply the same stored-record policy alongside consent/cookie checks.
Core ec/pull_sync.rs Keep deleted; provider orchestration remains in the shared application.
Core publisher.rs Supply the current snapshot to client filtering; retain current origin handling.
api-reference.md Retain current endpoint support descriptions.
axum-dev.md Retain prepared startup, persistent records and protected geo guidance.
configuration.md Preserve current activation guidance and document the read policy.

Removed Axum identity.rs, ec_kv.rs and their obsolete test module stay removed. The former EC policy-only flag is also unnecessary: #1646 deliberately keeps the configured record graph available without recognized fingerprint metadata.

Changes

Area Change
Core ownership Retain enabled owner IDs and consult only the matching EC row's active opt-outs. SharedID read policy checks both normalized aliases (pubcid.org and sharedid.org), closing opposite-alias/trailing-dot bypasses. Existing source-specific consent and write ownership remain unchanged.
Core egress Filter direct/publisher/page-bids client IDs and stored EIDs; apply the same legacy expiry and opt-out policy to identify and admin preview. No schema migration or extra write is introduced.
Axum acceptance Replace the former adapter-local setup with a real executable subprocess using prepared config/secret stores and persistent records. Exercise positive delivery, repeated cookie/body suppression, unrelated IDs and cookie opt-back-in.
Documentation Update the supporting spec/plan and provider guidance for the shared lifecycle, persistent records, geo and current stack.

All #1555 acceptance criteria are implemented here. Shared lifecycle/provider activation belongs to #1646, write-back to #1624, record binding to #1641, prepared startup to #1635, bounded follow-up work to #1613, and the environment guard to #1637.

Closes

Closes #1555

Spec

Not a feature: bug fix, with no configuration or persisted-schema change.

Design and plan.

An opt-out applies while its deadline is strictly greater than the request time and an enabled owner claims the source. Client EIDs cannot clear active memory. Missing, failed or mismatched snapshots retain existing degraded behavior. Legacy expiry is read-time suppression; rollback can resume serving old singles.

Geo and native startup

Axum production verification uses geo-cloudfront, prepared config/secret stores, isolated persistent records, an admitted loopback peer, the existing protected-origin credential/header mechanism, checked forwarding metadata and country AU, following the native acceptance setup. Geo selection uses supported EdgeZero startup options. No runtime environment reads were added, and the legacy TRUSTED_SERVER_CONFIG_* / TRUSTED_SERVER_SECRET_* bridge is not used for feature activation.

The default geo-off configuration still has unknown jurisdiction and fails identity use closed. The earlier claim that the native executable has no usable geo capability is obsolete: the configured protected-country production path now runs successfully. Migration of the pre-existing narrowly guarded geo profile compatibility input remains owned by #1529/#1532.

Test plan

Local checks passed on the merged source tree committed as d72c8bb37; Rust 1.98.1, Node 24.20.0 and isolated stock Viceroy 0.21.0. Release artifacts omit debug symbols.

  • cargo test-fastly: 239 adapter tests and 3,781 core tests passed; provider/JS/OpenRTB and documentation tests also passed.
  • cargo test-fastly-reuse: 239 adapter tests passed.
  • cargo test-axum --features geo-cloudfront: 119 tests passed, including the new prepared-store executable regression.
  • cargo clippy-fastly and cargo clippy-axum.
  • Identity guard: 9 passed. Cross-adapter parity: 33 passed.
  • Runtime environment guard compiler fixtures: 52 passed.
  • Rust format, changed documentation format and URL-host lint against the new base.
  • HTML EOF harness: 16 passed; harness lint passed. Real Axum and Fastly EOF/auction controls passed, including Fastly streaming.
  • 28 bidder-capture scenarios on each refreshed production runtime: positive delivery, no-provider cookie/body controls, legacy browser expiry on all three auction paths, real cookie opt-out across repeated visits, seeded remembered-policy enforcement with the cookie absent, unrelated-ID preservation, and real new-provider-cookie opt-back-in.
  • 14 pre-refresh Fastly bidder-capture controls on ee7a11031: no-provider cookie/body/initial/page-bids, repeated remembered-policy suppression and expired-memory delivery. Its strict JA4 gate under stock Viceroy prevents qualifying creation/provider transitions or positive stored-ID enrichment; those controls are not claimed.
  • Hosted CI on d72c8bb37: all 29 checks and all six workflows completed successfully. No failures or reruns.

Remembered server state is explicitly fixture-seeded: native uses a typed KvEntry, the production record adapter and exact-generation conditional write while the process is stopped; Fastly uses equivalent valid manifest state. Subsequent reads, filtering and cookie opt-back-in execute the normal release binaries. These results do not establish an HTTPS vendor response creating that memory, live-vendor behavior, deployed-edge behavior or real-browser behavior.

Hosted CI results

Every check below passed on d72c8bb37f4133bc81074270feb2cc28a10c88f3 against base c054ece709457dd4420aac27ccbb40c57e8c1cb0. All six workflows completed; no failures or reruns.

Check Result
browser integration tests Passed
cargo check (cloudflare native + wasm32-unknown-unknown) Passed
cargo check/build/test (spin native + wasm32-wasip1) Passed
cargo fmt Passed
cargo test Passed
cargo test (axum native) Passed
cargo test (cross-adapter parity) Passed
cargo test (ts CLI, native) (macos-latest) Passed
cargo test (ts CLI, native) (ubuntu-latest) Passed
CI Node pin guard Passed
CLAUDE.md symlink guard Passed
docs-proposal scripts Passed
Fastly response diff script Passed
format-docs Passed
format-typescript Passed
HTML EOF runtime (Fastly) Passed
integration tests Passed
integration tests (Fastly EC lifecycle) Passed
local-provider-image Passed
Native provider acceptance script Passed
prepare integration artifacts Passed
record-provider-image Passed
release scripts Passed
stock-celld-records Passed
trace runtime and browser acceptance Passed
ts dev lint domains (changed lines) Passed
vitest Passed
worker-deadlines (cloudflare) Passed
worker-deadlines (spin) Passed

Independent final source/evidence checks found zero blocking code findings and zero optional findings. Code review and CI are clear. Overall requested qualification remains blocked on the HTTPS producer transition described below; no review comments or replies were posted.

Draft and remaining qualification

Keep Draft for the outstanding requested HTTPS provider-response-to-persisted-memory runtime qualification. Code review, all local checks and all hosted checks are clear. The earlier merge-conflict and configured-native-geo blockers are resolved. This still depends on open #1646 and its stack; that dependency must land first.

The requested full provider-response-to-memory runtime qualification remains unverified. Native EdgeZero's production transport has no supported per-process fixture CA/routing override, and the current Fastly transport rejects predeclared backend-name collisions, preventing the old plaintext remap technique. No SDK guard or system trust setting was weakened. A supported local HTTPS fixture/trust/routing facility belongs in EdgeZero; no EdgeZero implementation was added here. See the pinned native transport and Fastly backend ownership handling. Broader provider/browser qualification remains tracked by #1581.

Checklist

  • Changes follow repository conventions; focused behavior has regressions.
  • No operator configuration, environment files or credentials changed.
  • No removed adapter-local implementation restored; no new runtime environment reads.
  • No comments or review-thread replies posted; only this PR's branch/base/description updated.

Runtime artifact receipts

Release artifacts were built with Rust 1.98.1 and Node 24.20.0, with debug symbols omitted. Both refreshed runtimes passed 28 bidder assertions plus the explicit seeded-memory receipt; the pre-refresh control passed 14 bidder assertions within its stated scope.

Artifact SHA-256
Refreshed Axum production executable, geo-cloudfront dc6abc25fcd17ae55b0bc7abef101aa2ac81045970174568b9a77ed86f617778
Refreshed Fastly production WASM 16fab5296b5994d62e8c96df0b1f887d22589ad4d4297b298e57a148f4597fe7
Pre-refresh ee7a11031 Fastly control 3d097e426db136cd6879ba6eabf7d2818e278586f7b5ce74edd525e6937dda4d

Axum now builds the partner registry and both provider coordinators at startup, reads and mints ts-ec on publisher navigations, runs page-phase lookups through Axum's HTTP client, and finalizes through KvIdentityGraph with a single page-load write. After-response providers run on a spawned blocking task with their follow-up compare-and-swap write. The identity graph is a process-local store with generation-based CAS, enabled when ec.ec_store is set.

Signed-off-by: dhruv8sh <dhruv8sh@proton.me>
Signed-off-by: dhruv8sh <dhruv8sh@proton.me>
Signed-off-by: dhruv8sh <dhruv8sh@proton.me>
@prk-Jr prk-Jr self-assigned this Nov 18, 2026
@prk-Jr prk-Jr linked an issue Nov 18, 2026 that may be closed by this pull request
3 tasks
@prk-Jr prk-Jr changed the title Enforce provider opt-outs for client and legacy EIDs Enforce provider opt-outs and legacy EID expiry on Fastly and Axum Nov 18, 2026
@prk-Jr
prk-Jr changed the base branch from feat/s2s-eid-vendors to feat/axum-identity-providers November 18, 2026 15:19
@prk-Jr
prk-Jr force-pushed the fix/1555-provider-eid-opt-outs branch from 7ac8b5e to ee7a110 Compare November 18, 2026 15:19
@prk-Jr
prk-Jr added this pull request to stack #1629 November 18, 2026 16:25
@dhruv8sh
dhruv8sh removed this pull request from stack #1629 November 20, 2026 01:58
@prk-Jr
prk-Jr changed the base branch from feat/axum-identity-providers to feat/1574-axum-shared-identity November 20, 2026 09:49
@prk-Jr
prk-Jr added this pull request to stack #1649 November 20, 2026 09:50
@prk-Jr
prk-Jr marked this pull request as ready for review November 20, 2026 10:24

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Client and browser EIDs for provider-owned sources after a provider opt-out

2 participants