OIDF · date: see source
OpenID Continuous Access Evaluation Profile 1.0
openid-caep-1_0-final
OIDF FinalStableAuthorizationAdjacent
Agent sessions are long. CAEP is how you implement 'kill the agent' as a protocol, not a Slack message to on-call.
At a glance
- Problem
- Access decisions made at token-issuance time go stale. CAEP defines event types so cooperating systems can attenuate access when sessions, credentials, or device posture change — including for robotic users.
- Identity / authn / authz
- Authorization continuity. Explicitly mentions shared human or robotic users.
Actors
- SSF transmitter
- SSF receiver (agent platform, MCP host, SaaS)
When this matters for agents
When this matters for agents: CAEP is how you implement 'kill the agent' as a protocol (session-revoked, credential-change), including for robotic users. It does not issue tokens; it tells you to stop trusting ones you already have.
Flow in plain language
Same transport as SSF. Event types under https://schemas.openid.net/secevent/caep/event-type/ including session-revoked and credential-change.
Key tokens and claims
- credential-change
- Signals create/change/revoke/delete of passwords, FIDO, VCs, app credentials, …
Implementer notes
CAEP does not issue tokens; it tells you to stop trusting ones you already have.
Relationship to others
Primary sources
- CAEP 1.0https://openid.net/specs/openid-caep-1_0-final.html