RFC 9967 (SCIM Profile for Security Event Tokens)
RFC 9967 · RFC9967 · draft-ietf-scim-events
IETF standard that carries SCIM (System for Cross-domain Identity Management) events as Security Event Tokens, so service providers and receivers exchange messages asynchronously. It also adds an optional asynchronous SCIM request mode.
In our briefings
The claim each of the newest briefings on RFC 9967 (SCIM Profile for Security Event Tokens) would have you leave with.
Under RFC 9967 a SCIM event reports a change, and each receiver can choose its own follow-up; the authors say receivers do this "instead of interpreting SETs as commands". The deactivate event says a resource such as a User "has been deactivated and disabled", but its exact meaning SHOULD be agreed between the event publisher and the receiver. The RFC adds only that this typically means the subject may no longer have an active security session. The activate event "does not necessarily reflect any particular state change" either.
RFC 9967 lets SCIM report a deactivated account and leaves what that means to each sender and receiverBI-FIND-2026-1697
Cited in 1 briefing
Every briefing that discusses this term, newest first.
- RFC 9967 lets SCIM report a deactivated account and leaves what that means to each sender and receiver
Article · · RFC Editor · Phil Hunt et al. · May 14, 2026
Related terms
What appears alongside RFC 9967 (SCIM Profile for Security Event Tokens) in the same briefings.
Coordinated Provisioning (SCIM events)Domain-Based Replication (SCIM events)RFC 7644 (SCIM Protocol)Security Event Token (SET)RFC 7643 (SCIM Core Schema)