Skip to content

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

Open

Description

@dhruv8sh

Follow-up from PR #1487.

Description

After a provider opt-out clears its sources, a client EID for the same source (from the ts-eids cookie or the /auction body) still reaches bidders. A browser record stored in a provider-owned source is also served indefinitely. PR A filters client copies only by withheld vendor consent.

Reproduction steps

  1. Configure an enabled identity provider (fictional example: example-provider, https://id.example.com).
  2. Exercise the path described above with a test EC (for example ec-0000-test).
  3. Observe the behaviour described.

Expected behavior

Read the row's opt_outs on /auction and page-bids, and drop client EIDs for the sources of an opted-out provider. Expire browser-written records in provider-owned sources.

Acceptance criteria

  • /auction and page-bids read the row's opt_outs and drop client EIDs for sources of an opted-out provider.
  • Browser-written records in provider-owned sources expire.
  • With no providers configured, output is unchanged; tests cover cookie and request-body EIDs.

Affected area

Core (Edge Cookies, GDPR)

Code: crates/trusted-server-core/src/auction/endpoints.rs (drop_vendor_denied_client_eids, merge_auction_eids); publisher.rs (apply_auction_eids_and_device); ec/eids.rs (live_eids).

Version

main with PR #1487 (feat/s2s-eid-after-response).

Review threads

Activity

  1. added this to the 202611 milestone on Nov 11, 2026
  2. self-assigned this
    on Nov 11, 2026
  3. added theissue type on Nov 11, 2026
  4. dhruv8sh commented on Nov 12, 2026

    @dhruv8sh
    CollaboratorAuthor

    Related change in #1487 (e6b22d2): a remembered provider opt-out now clears only the provider sources the stored row still holds. Client and browser copies covered by this issue are unaffected by that change.

  5. aram356 commented on Nov 13, 2026

    @aram356
    Collaborator

    CREATOR: This issue is now part of #1558, server-side identity on every adapter. It is planned in wave 4 (MVP: Fastly and Axum); priority P2, size S.

    Blocked by:

    Related pull requests:

    Design: spec; order and dependencies: plan.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions