search

ietf-scim-wg / draft-ietf-scim-events

Working material for the IETF SCIM Events draft
Other
5 stars 3 forks source link

Relative path in sub_id.urn while absolute paths are common #30

Closed arietimmerman closed 7 months ago

arietimmerman commented 11 months ago

It is specified that sub_id.urn must contain the relative path for the resource. I wonder why, since the SCIM protocol uses absolute paths in meta.location. To me it makes more sense to include absolutes path in sub_id.urn as well.

https://github.com/ietf-scim-wg/draft-ietf-scim-events/blob/a6919a3feb10ea5d0784578225f7bf6386908dbf/draft-ietf-scim-events-04.xml#L286C27-L286C27

independentid commented 11 months ago

Arie,

The same event may be sent to more than one receiver (multiple audiences). Each receiver may have a unique URL for the SCIM service (RFC7644) access. Using relative allows the event to be sent to multiple receivers.

Phil @.***

On Dec 21, 2023, at 3:07 AM, Arie Timmerman @.***> wrote:

It is specified that sub_id.urn must contain the relative path for the resource. I wonder why, since the SCIM protocol uses absolute paths in meta.location. To me it makes more sense to include absolutes path in sub_id.urn as well.

https://github.com/ietf-scim-wg/draft-ietf-scim-events/blob/a6919a3feb10ea5d0784578225f7bf6386908dbf/draft-ietf-scim-events-04.xml#L286C27-L286C27

— Reply to this email directly, view it on GitHub https://github.com/ietf-scim-wg/draft-ietf-scim-events/issues/30, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFQUXWSKFQSOA7ZNCMBCE3YKQJ57AVCNFSM6AAAAABA6HDEDGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA2TEMRRGQYDMNA. You are receiving this because you are subscribed to this thread.