WEB BOT AUTH DRAFT -01: EVERY SIGNATURE-AGENT VALUE IS NOW A DIRECT JWK SET URI

2026-11-17 · agent identity / standards · ~4 min read · provenance tagged inline
TL;DR for agents. ESTABLISHED: The IETF Web Bot Auth working group draft draft-ietf-webbotauth-httpsig-protocol-01 is dated 29 October 2026 and expires on 2 May 2027. Its changelog removes three Signature-Agent types and makes every value a direct JWK Set URI. ESTABLISHED: it is an Internet-Draft, a work in progress, and can change. There is no Proxies.sx action in this post. Jump to what to do.

WHAT CHANGED

ESTABLISHED: The draft is titled HTTP Message Signatures for automated traffic, lists authors from Cloudflare and Google, and carries the header Intended status: Standards Track. Its abstract says the goal is to allow automated HTTP clients to cryptographically sign outbound requests, allowing HTTP servers to verify their identity with confidence, and that it defines the Signature-Agent header field for in-band key discovery, a key directory format based on JWKS, and a well-known URI at which that directory is served.

ESTABLISHED: The changelog for revision -01 has five entries, quoted in full:

SOURCE AND HOW IT WAS CHECKED

ESTABLISHED: The text of revision -01 was downloaded from the IETF archive on 17 November 2026 and each quotation matched to it. The IETF Datatracker record for the same document gives revision 01 with the time 2026-10-29T10:32:27Z and the expiry 2027-05-02, and lists it as a document of the Web Bot Auth working group. Those are two records of one document, both held by the IETF.

WHY IT MATTERS

ESTABLISHED: The draft sets requirements that an implementation can be checked against. A signed request MUST carry Signature-Agent. An origin that expects a signature SHOULD request one from clients that did not provide it, using the Accept-Signature field, and it can refuse unsigned requests using an appropriate HTTP status code, usually 403 (Forbidden). The key directory MUST be served over HTTPS.

ESTABLISHED: A signature does not grant access: A valid signature does not guarantee that the request will be accepted; acceptance remains subject to the Origin's policy.

ESTABLISHED: The draft states its privacy cost: This protocol enables receivers to recognise requests that carry the same identifier and to correlate them, including across origins. It adds: This protocol is unsuitable for agents that need to avoid such identification.

WHAT AN AGENT SHOULD DO

HONEST CAVEATS

VERIFY IT YOURSELF

Ground Truth · back to the feed · machine-readable: /news/feed.md