[scim] SCIM Events and Subject Identifiers Proposed Standard

[Phillip Hunt <[e-mail]>]

FYI.  The Subject Identifiers draft which the SCIM Events depends on has been approved (meaning it will an RFC shortly).

I will update the SCIM Events draft to reference the new version.

I believe that the OpenID Shared Signals group is also looking at depending on this draft for RISC and CAEP security events.

==> For the SCIM Events draft, the use of Subject Identifiers allows more flexibility for non-SCIM receivers to match SCIM Resources to local entities. In the initial proposal only SCIM Id and externalId was used.  As detailed in the draft, a SCIM Event’s publisher is able to issue other unique identifiers like username, email etc.

Phillip Hunt
[e-mail]





> Begin forwarded message:
> 
> From: The IESG <[e-mail]>
> Subject: [Id-event] Protocol Action: 'Subject Identifiers for Security Event Tokens' to Proposed Standard (draft-ietf-secevent-subject-identifiers-18.txt)
> Date: June 26, 2023 at 11:09:05 AM PDT
> To: "IETF-Announce" <[e-mail]>
> Cc: The IESG <[e-mail]>, [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail]
> 
> The IESG has approved the following document:
> - 'Subject Identifiers for Security Event Tokens'
>  (draft-ietf-secevent-subject-identifiers-18.txt) as Proposed Standard
> 
> This document is the product of the Security Events Working Group.
> 
> The IESG contact persons are Paul Wouters and Roman Danyliw.
> 
> A URL of this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/
> 
> 
> 
> 
> 
> Technical Summary
> 
>   Security events communicated within Security Event Tokens may support
>   a variety of identifiers to identify subjects related to the event.
>   This specification formalizes the notion of subject identifiers as
>   structured information that describe a subject, and named formats
>   that define the syntax and semantics for encoding subject identifiers
>   as JSON objects.  It also defines a registry for defining and
>   allocating names for such formats, as well as the sub_id JSON Web
>   Token (JWT) claim.
> 
> Working Group Summary
> 
> There was nothing notable in the WG process beyond the long dormancy this document had.
> 
> Document Quality
> 
> This is a dependency of the GNAP WG, and GNAP participants have been involved in the later development stages of this draft.
> 
> Personnel
> 
> - Document Shepherd:  Yaron Sheffer
> - Responsible AD: Roman Danyliw
> 
> _______________________________________________
> Id-event mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/id-event