# Real-time access signals (SSF and CAEP)

When a customer's IT admin disables a user or revokes their sessions, your app should know within seconds, not at the next sign-in. OhAuthCat speaks the OpenID Shared Signals Framework (SSF 1.0) with the CAEP and RISC event types, and merges what it hears with SCIM changes into a single `access.changed` event.

## Receiving from identity providers

OhAuthCat registers as an SSF receiver with an IdP that supports it (Okta, for example): it reads the IdP's `/.well-known/ssf-configuration`, creates a stream, and accepts pushed Security Event Tokens or polls for them. Every token is checked before use: signature against the transmitter's keys, exact issuer and audience, single use of its `jti`, and a recent issue time. A token that fails any check is dropped (fail closed).

Events understood: CAEP `session-revoked`, `credential-change`, `assurance-level-change` and `device-compliance-change`; RISC `account-disabled`, `account-purged` and `identifier-changed`.

## One stream for your app: `access.changed`

Your app receives `access.changed` webhooks when access ends or changes for a user, whatever the source:

- an SSF or CAEP signal from the IdP;
- a SCIM deactivation or deletion;
- OhAuthCat itself detecting a replayed sign-in code.

Handle it by ending the user's sessions in your app. See the [webhook event catalogue](/reference/webhook-events/).

## Transmitting to your receivers

OhAuthCat is also an SSF transmitter. Your own services, or a security tool, can subscribe to signed `access.changed` signals:

- metadata at `/.well-known/ssf-configuration` on the signals host, and signing keys at `/ssf/jwks`;
- stream management at `/ssf/streams` (create, read, update, replace, delete), stream status and verification;
- delivery by push to your endpoint (RFC 8935) or by poll (RFC 8936).

You can also manage streams with your secret key on the management API: `GET` and `POST /v1/ssf_streams`, `GET`, `PATCH` and `DELETE /v1/ssf_streams/{stream}`, and `POST /v1/ssf_streams/{stream}/verify` to send a verification event (scopes `signals:read` and `signals:write`). Each change is recorded in your audit log. From the CLI: `ohauthcat ssf streams list|get|create|update|delete|verify`; in Terraform: `ohauthcat_ssf_stream`. Access signals are a Business and Enterprise feature.
