2. SCIM Events
SCIM Events use the URI prefix urn:ietf:params:scim:event. Events are grouped into feed, prov, and misc classes. SCIM Events MUST use the sub_id claim from RFC 9493 to identify the subject. sub_id MUST be in the main JWT claims body and MUST NOT be inside an event payload in the events claim. The JWT sub claim MUST NOT be used for subjects. The top-level sub_id claim SHALL be used, with format set to "scim"; sub_id.uri MUST be provided.
For all events defined here, exactly one of data or attributes is used according to the event definition. For provisioning events, if data is present, the event URI MUST end with full; otherwise it ends with notice. Exactly one of data or attributes MUST be present, and both MUST NOT be present simultaneously.
| Class | Event URI |
|---|---|
| feed | urn:ietf:params:scim:event:feed:add |
| feed | urn:ietf:params:scim:event:feed:remove |
| prov | urn:ietf:params:scim:event:prov:create:notice |
| prov | urn:ietf:params:scim:event:prov:create:full |
| prov | urn:ietf:params:scim:event:prov:patch:notice |
| prov | urn:ietf:params:scim:event:prov:patch:full |
| prov | urn:ietf:params:scim:event:prov:put:notice |
| prov | urn:ietf:params:scim:event:prov:put:full |
| prov | urn:ietf:params:scim:event:prov:delete |
| prov | urn:ietf:params:scim:event:prov:activate |
| prov | urn:ietf:params:scim:event:prov:deactivate |
| misc | urn:ietf:params:scim:event:misc:asyncresp |
Important distinctions: feed:add and feed:remove change event-feed membership and do not imply create, delete, or deactivate. prov:delete has no payload attributes and uses neither full nor notice. deactivate meaning SHOULD be agreed by Event Publisher and Event Receiver.