Repository navigation
Conversation
1 task
The merge applied without conflicts. The Prebid integration config keeps this pull request's mode field next to the base's changes, and the example config, the Prebid guide and the tsjs Prebid sources take both sides unchanged. The server mirror cookie the identity mode reads is the same name and envelope in the base, so no code needed to change.
Collaborator
|
For the identity integration chain (#1608), this PR's base #1489 was ported onto #1506's EdgeZero cutover and #1526's async store, so Checked locally at |
20 of 21 tasks
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
integrations.prebid.mode = "identity"so publishers can use managed Prebid identity without installing Trusted Server's browser auction integration. Existing configurations default to"auction".ts-eids, including pages that never run an auction.Stacked on #1489, targeting
feat/s2s-eid-collection-providers; the mirror writer must land first.Enable identity-only mode
Update the existing table in your application configuration and publish the updated config:
Keep the existing external bundle, module selection and managed User ID settings. Add or update
modein the existing table; do not create a duplicate TOML table. Deploying the code alone does not enable this mode. Omittedmodedefaults to"auction".See the identity-only setup guide.
Changes
crates/trusted-server-core/src/integrations/prebid.rscrates/trusted-server-js/lib/src/integrations/prebid/index.tscrates/trusted-server-js/lib/src/integrations/prebid/native_capture.tscrates/trusted-server-js/lib/src/integrations/prebid/identity.tscrates/trusted-server-js/lib/test/integrations/prebid/identity.test.tscrates/trusted-server-js/lib/test/prebid-artifact-integration.test.mjsdocs/guide/integrations/prebid.mdtrusted-server.example.tomldocs/superpowers/specs/2026-11-17-identity-only-tsjs-design.mddocs/superpowers/plans/2026-11-17-identity-only-tsjs.mdCloses
Closes #1594
Spec
Spec: Identity-only tsjs mode, including two agent review rounds.
Test plan
cargo test-fastly && cargo test-fastly-reuse && cargo test-axum && cargo test-cloudflare && cargo test-spincargo fmt --all -- --checkBrowser verification exercised the actual Fastly and Axum applications, trusted HTTPS development proxy, real Chrome and a controlled bidder. Seven reader scenarios per adapter cover native capture before any auction, mirror delivery/removal/replacement/expiry/malformed input, metadata precedence, consent denial/restoration and no mirror echo. The controlled reader fixture supplied a generated Prebid 10.26 bundle and synthetic mirror; the application injected and served the changed tsjs normally.
A separate operator-config run used the configured publisher origin and external Prebid bundle, without manual
requestBidscalls. Automatic native capture was observed on the Fastly homepage and an Axum article; captured IDs matched the native getter and unchanged samples did not rewrite the cookie. Some repeated publisher runs encountered external bundle/origin timeouts or absent third-party identity setup, so these observations do not qualify third-party reliability.Subsequent deployed Fastly staging verification passed six controlled cookie-provider scenarios: provider input, replacement, opt-out, restoration, and persisted-ID reuse after removing the provider input, carried mirror and native capture cookies. The server reissued the mirror and the actual deployed Prebid bidder consumer received the expected ID without mirror echo. The controlled bidder returned no HTTP requests; these checks do not qualify live vendor APIs, bidder HTTP delivery or other provider kinds. The served shim matched the reviewed build; the backend version header identified the branch rather than an exact commit. Local Viceroy still lacks the JA4 metadata required for normal provider activation, and Axum does not support enabled providers.
Checklist
unwrap()added in production codelogmacros (notprintln!)