Skip to main content
Agent Identity

IETF · 30 October 2026

WIMSE Workload Credentials

draft-ietf-wimse-workload-creds-03

WG draftDraft — expect changeIdentityAgent-specificField guide

WIMSE Workload Credentials (draft-ietf-wimse-workload-creds-03) is WG draft, 30 October 2026. This is the 'agent identity document' in the WIMSE world, analogous to AAuth's agent token but scoped to workload trust domains.

ShareLinkedInX

At a glance

Problem
Bind a public key to a workload identifier in a credential that must not be used as a bearer token.
Identity / authn / authz
Identity credential. Proof-of-possession is specified in companion drafts (WPT, HTTP signature, mTLS).

Actors

  • Identity server
  • Workload
  • Relying party

01

The gap for agents

Bind a public key to a workload identifier in a credential that must not be used as a bearer token. This is the 'agent identity document' in the WIMSE world, analogous to AAuth's agent token but scoped to workload trust domains that share configured trust anchors.

02

Actors and trust boundaries

Trust anchors for a trust domain are configured out of band. Validators select them from the trust domain in sub. iss is recommended for audit and is not how you discover keys: resolving iss to a JWKS would accept any issuer that can publish one. That is stricter than typical OAuth AS JWKS discovery — on purpose.

03

Mechanics

draft-ietf-wimse-workload-creds-03, 30 October 2026, expires 3 May 2027. Workload Identity Token: JWS JWT, typ wit+jwt, sub = identifier, exp (hours-scale), cnf.jwk with alg (ES256 MUST be supported; none and symmetric/encryption algs forbidden). Conveyed in Workload-Identity-Token header — not Authorization. Workload Identity Certificate: X.509 with a single URI SAN, SPIFFE-compatible. Draft-03 adds a WIT validation procedure. Authors include B. Campbell, J. Salowey, A. Schwenkschuster, Y. Sheffer, Y. Rosomakho.

typ: wit+jwtfrom spec
Quoted: explicit typing per RFC 8725.
cnf.jwk + algfrom spec
Quoted: public key of the workload. Proof of that key is mandatory. MUST NOT be used as a bearer token; not intended for Authorization.
Workload-Identity-Token headerfrom spec
Quoted HTTP field for presenting a WIT.
WIC (X.509)from spec
Quoted: transport-layer identity certificate; URI SAN.

04

Step-by-step flows

Flow 1

Issue and present a WIT

  1. 1

    Identity server mints wit+jwt with sub, cnf.jwk, exp on the order of hours.

  2. 2

    Workload presents Workload-Identity-Token plus a WPT (or HTTP signature) proving cnf.

  3. 3

    Recipient validates against configured trust anchors for the trust domain in sub, then the proof.

  4. 4

    On WIT validation failure, HTTP 400 with RFC 9457 problem details is the typical response. HTTP 401 is only recommended when an acceptable WWW-Authenticate mechanism exists for that error.

05

Identity vs authentication vs authorization

Identity credential. Proof-of-possession is specified in companion drafts (WPT, HTTP signature, mTLS). Authorization context (Txn-Tokens, OAuth) rides in other headers.

06

How it composes

  • WIMSE WPT

    Application-layer PoP.

  • SPIFFE / SPIRE

    WIC aligns with X509-SVID practice.

  • JWT

    WIT is a typed JWT profile.

  • Transaction Tokens

    Explicitly allowed alongside WIT; different header.

  • AAuth

    Similar 'JWT + key + not bearer' idea; different typ, discovery, and trust-anchor story.

07

What bites agent implementers

  • JWKS from iss

    Forbidden as the sole trust source. Configure anchors per trust domain.

  • Authorization: Bearer WIT

    The draft says not intended for Authorization and MUST NOT be used as bearer. Use WPT's Authorization: WPT scheme instead.

08

Stability — what you can ship

draft-ietf-wimse-workload-creds-03, 30 October 2026, expires 3 May 2027, standards-track WG. https://datatracker.ietf.org/doc/html/draft-ietf-wimse-workload-creds-03

Catalog claims (short form)

WIT (JWS JWT)
Application-layer identity token; not bearer.
WIC (X.509)
Transport-layer identity certificate; URI SAN.

Implementer notes

WIT in sub, WIC in a single URI SAN. Aligns with X509-SVID practice.

Related

Primary sources

  • HTML of draft-03https://datatracker.ietf.org/doc/html/draft-ietf-wimse-workload-creds-03