[scim] Re: [Technical Errata Reported] RFC7643 (8366)

[Phil Hunt <[e-mail]>]

This errata requires some discussion.

It is possible someone might somehow define multiple resourcetypes to the same endpoint for aliasing or migration purposes.

Any concerns in amending to uniqueness as “server”?

I think this would result in a hidden normative change that may have an impact.


Phil Hunt
[e-mail]



> On Apr 1, 2025, at 12:51 AM, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC7643,
> "System for Cross-domain Identity Management: Core Schema".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid8366
> 
> --------------------------------------
> Type: Technical
> Reported by: Matthias Winter <[e-mail]>
> 
> Section: 8.7.2
> 
> Original Text
> -------------
>      {
>        "name" : "endpoint",
>        "type" : "reference",
>        "referenceTypes" : ["uri"],
>        "multiValued" : false,
>        "description" : "The resource type's HTTP-addressable
>          endpoint relative to the Base URL, e.g., '/Users'.",
>        "required" : true,
>        "caseExact" : false,
>        "mutability" : "readOnly",
>        "returned" : "default",
>        "uniqueness" : "none"
>      },
> 
> Corrected Text
> --------------
>      {
>        "name" : "endpoint",
>        "type" : "reference",
>        "referenceTypes" : ["uri"],
>        "multiValued" : false,
>        "description" : "The resource type's HTTP-addressable
>          endpoint relative to the Base URL, e.g., '/Users'.",
>        "required" : true,
>        "caseExact" : false,
>        "mutability" : "readOnly",
>        "returned" : "default",
>        "uniqueness" : "server"
>      },
> 
> Notes
> -----
> For "endpoint" the property "uniqueness" should be "server" instead of "none".
> I believe endpoints are thought to be unique within a server, i.e. each endpoint should offer exactly one type of resources. Though I don't see any point in RFC7644 or RFC7643 that currently forbids using the same endpoint for several resource types, it would make processing much harder for clients. Also, clients cannot specify which resource type they want to create. They can only specify endpoint and schema.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it 
> will be removed shortly by the RFC Production Center.) Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> will log in to change the status and edit the report, if necessary.
> 
> --------------------------------------
> RFC7643 (draft-ietf-scim-core-schema-22)
> --------------------------------------
> Title               : System for Cross-domain Identity Management: Core Schema
> Publication Date    : September 2015
> Author(s)           : P. Hunt, Ed., K. Grizzle, E. Wahlstroem, C. Mortimore
> Category            : PROPOSED STANDARD
> Source              : System for Cross-domain Identity Management
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> scim mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]