shared-signals.dev

Specifications

The specifications

Three OpenID Foundation final specifications, one interoperability profile, and the IETF RFCs underneath them, developed in the open by the Shared Signals Working Group — plus SCIM events, the IETF’s provisioning events that travel the same way.

Final Shared Signals Framework 1.0

The framework everything else plugs into. Defines subject principals and identifiers, how SSF uses SETs, Transmitter discovery, the stream management API (create, read, update, delete, status, subjects, verification), and how push and poll delivery are profiled.

Read SSF 1.0 → · Our walkthrough

Final Continuous Access Evaluation Profile (CAEP) 1.0

Event types for continuously re-evaluating access during a session: session revoked, established and presented; token claims change; credential change; assurance level change; device compliance change; and risk level change. Also defines optional claims common to all CAEP events — event_timestamp, initiating_entity, reason_admin and reason_user.

Read CAEP 1.0 → · CAEP event types

Final Risk Incident Sharing and Coordination (RISC) 1.0

Account-level events for coordinating responses to compromise across providers: credential compromise, account disabled / enabled / purged, identifier changed or recycled, recovery activity, and opt-in/opt-out. RISC's sessions-revoked is deprecated in favour of CAEP's session-revoked.

Read RISC 1.0 → · RISC event types

Draft 01 CAEP Interoperability Profile 1.0

Narrows the options in SSF and CAEP to a common baseline so independently built Transmitters and Receivers work together out of the box: required discovery fields, push and poll delivery, OAuth with the ssf.read / ssf.manage scopes, email and iss_sub subjects, RS256 signing, and four use cases — session revocation, credential change, device compliance change and (new in the working copy) risk level change. Draft 01 went to public review as a proposed Final in July 2026; in September the working group chose to revise it and restart review. If you are building something new, start here.

Our requirements checklist → · Draft 01 · Working copy

RFC SCIM Events (RFC 9967)

The IETF SCIM working group’s profile for sending provisioning changes as Security Event Tokens, published in May 2026. A SCIM service provider tells receivers that a user or group was created, patched, replaced, deleted, activated or deactivated, or that a resource joined or left an event feed. Provisioning events come in a :full variant carrying the data and a :notice variant listing only the changed attributes. It also defines asynchronous SCIM requests, whose completion arrives as an event. Subjects use a new sub_id format, scim, holding the resource’s uri, and event types are URNs under urn:ietf:params:scim:event:. Delivery uses the same push and poll RFCs as SSF, so SSF Transmitters and Receivers can carry SCIM events alongside CAEP and RISC. It updates RFC 7643 and RFC 7644.

Read RFC 9967 → · SCIM event types · Send one from the playground

Status at a glance

DocumentStatusLatest
Shared Signals Framework 1.0Final2025-08-29 — no changes since
CAEP 1.0Final2025-08-29 — no changes since
RISC 1.0Final2025-08-29 — no changes since
SCIM Events (RFC 9967)IETF Standards Track RFCMay 2026
CAEP Interoperability Profile 1.0Proposed Final — being revised; public review to restartDraft 01 July 2026; working copy adds Risk Level Change (2026-09-01)

Checked against openid/sharedsignals @ a34d6ff (2026-09-01) on 2026-10-18. The repository also holds older, inactive drafts (OAuth Event Types, RISC use cases, subject identifier scenarios) that are not covered here. Working copies of everything are published at openid.github.io/sharedsignals.

Underlying IETF standards

RFCTitleRole in SSF
RFC 8417Security Event Token (SET)The JWT format every SSF event is carried in.
RFC 8935Push-Based SET Delivery Using HTTPTransmitter POSTs SETs to the Receiver.
RFC 8936Poll-Based SET Delivery Using HTTPReceiver polls the Transmitter and acknowledges SETs.
RFC 9493Subject Identifiers for Security Event TokensThe email / iss_sub / opaque / … subject formats.
RFC 7519JSON Web Token (JWT)The token format underneath SETs.
RFC 9967SCIM Profile for Security Event TokensSCIM provisioning events carried as SETs; see SCIM events above.
RFC 6749OAuth 2.0The usual way Receivers authorise to the stream management API.

Following the work