Repository navigation
Closed as not planned
Closed as not planned
Copy link
Labels
claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.needs-wg-reviewBlocked on a working-group decision — surface in WG meeting agendasBlocked on a working-group decision — surface in WG meeting agendasschemaJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygieneJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygiene
Milestone
Description
Context
In AdCP 3.x, authentication is required on:
static/schemas/source/core/reporting-webhook.jsonartifact_webhookblock ofstatic/schemas/source/media-buy/create-media-buy-request.json
This forces every receiver into the deprecated Bearer / HMAC-SHA256 path even though the canonical signing profile is RFC 9421 (seller signs with the key published at its brand.json agents[].jwks_uri; buyer verifies against the seller's JWKS).
The schema descriptions already advertise this: "This field is required in AdCP 3.x; the requirement is removed in AdCP 4.0 when the default RFC 9421 path becomes the only path" (landed in #4271).
Scope for 4.0
- Drop
"authentication"fromrequired[]inreporting-webhook.json. - Drop
"authentication"from theartifact_webhook.required[]block increate-media-buy-request.json. - Confirm the security doc's webhook-callbacks section covers signing-mode selection for both surfaces (it currently focuses on
push_notification_config); extend if not. - Decide whether to remove the
authenticationblock entirely or keep it as an optional opt-in for legacy receivers. Recommendation: keep optional in 4.0 with a 4.x removal target — gives sellers a one-major escape hatch.
Why this isn't 3.x
Per playbook, removing a required[] constraint is a signing-profile change and never patch-eligible. Description-only updates landed in #4271 (patch, 3.0.x). This issue tracks the structural change for the next major.
Refs
- [meta] Coordinate RFC 9421 webhook signing migration — adoption telemetry + threshold + ownership #4205 (parent — RFC 9421 migration coordination)
- Storyboard / SDK skill on-ramp inventory: HMAC vs RFC 9421 #4270 (storyboard / SDK on-ramp inventory — closed by fix(schema,skill): align HMAC framing to RFC 9421 default in reporting-webhook, auth-scheme, call-adcp-agent SKILL.md #4271)
- fix(schema,skill): align HMAC framing to RFC 9421 default in reporting-webhook, auth-scheme, call-adcp-agent SKILL.md #4271 (description-only fix, 3.0.x)
Metadata
Metadata
Assignees
Labels
claude-triagedIssue has been triaged by the Claude Code triage routine. Remove to re-triage.Issue has been triaged by the Claude Code triage routine. Remove to re-triage.needs-wg-reviewBlocked on a working-group decision — surface in WG meeting agendasBlocked on a working-group decision — surface in WG meeting agendasschemaJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygieneJSON Schema source-of-truth: definitions, codegen artifacts, validation, hygiene
Activity
bokelley commentedon May 9, 2026
Triage
Classification: Feature request — 4.0 structural schema change
Bucket(s): spec / protocol, security-sensitive
Status: ready-for-human
Milestone: 4.0 (#5)
What the experts said:
reporting-webhook.jsonandartifact_webhooklack the mode-switch precedence language already inpush-notification-config.json("presence of this block selects the legacy scheme; absence selects 9421; seller MUST NOT sign both ways"). Also flags scope gap:sync-governance-request.jsonhasrequired: ["url", "authentication"]on the governance-agent webhook surface and isn't included.artifact-webhook-payload.json(idempotency_key anchors to HMAC secret, not RFC 9421keyid) andper_principal_key_isolationenforcement for multi-tenant sellers onartifact_webhook. Credential-zeroing guidance is also missing from the migration path.My take: Experts split on A vs. B — protocol precedent points to A, security hygiene points to B. Both agree the
required[]drop alone is insufficient: the two schemas need description upgrades before this is shippable, andsync-governance-request.jsonis an unaddressed sibling surface.@bokelley, your call: Option A (keep optional, explicit sunset commitment) or Option B (remove in 4.0, clean break)?
Option A — Drop from required[], keep optional (one-major escape hatch):
Option B — Remove authentication entirely (clean break):
Either option should also address:
sync-governance-request.jsonauthentication surface,artifact-webhook-payload.jsonidempotency_key anchor, and the migration guide credential-zeroing requirement.Triaged by Claude Code. Session: https://claude.ai/code/${CLAUDE_CODE_REMOTE_SESSION_ID}
Generated by Claude Code
bokelley commentedon Oct 13, 2026
Filed #8176 to relax this in 3.3 rather than wait for 4.0:
authenticationbecomes optional onreporting_webhookandartifact_webhookonly for requests pinned to 3.3+ to a seller that declareswebhook_signing.supported: true, with the same presence/absence switch aspush_notification_config. That is a minor-release change (same pattern as theimpressionsloosening in #8089), so it does not conflict with the "not patch-eligible" reasoning here. This issue would still own the 4.0 decision to remove the block or keep it optional.bokelley commentedon Nov 8, 2026
Superseded. #8177 (merged 2026-10-20) made
authenticationoptional on reporting and artifact webhooks in 3.3, and full removal of webhookauthenticationis tracked for 4.0 in #8662.🤖 Generated with Claude Code