Skip to content

F24.2 — ID tokens refuse other profiles' types

State Closed
Parent E24
Iteration Release 9
Start Date 2026-11-17
Closed Date 2026-11-17
Predecessors —

Stories: 1 Closed

Story State Depends on
S24.2.1 — Check the ID token's typ Closed (2026-11-17) —

IdTokenVerifier checks the typ header as the RFC 7519 access profile does, so the module's claim that each profile's typ excludes the others holds. This reverses S22.8's "ID tokens keep no typ check" (owner, 2026-11-17).

S24.2.1 — Check the ID token's typ

State: Closed (2026-11-17)

Acceptance:

  • An ID token with no typ, or JWT in any case, verifies as before.
  • Any other typ, including at+jwt, application/at+jwt, logout+jwt and application/logout+jwt, raises TokenVerificationError naming the typ.
  • tests/oidc/test_id_token.py covers both; the profile matrix in tests/oidc/test_profiles.py still passes.

Settled contract: the check runs once the signing key resolves, before claim validation; the message is Token typ <typ> is not an ID token.