[scim] [Errata Held for Document Update] RFC7644 (8367)

RFC Errata System <rfc-editor@rfc-editor.org> Sun, 28 December 2025 15:32 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: scim@ietf.org
Delivered-To: scim@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 06372A00B574; Sun, 28 Dec 2025 07:32:15 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id C7A25C000CD7; Sun, 28 Dec 2025 07:32:14 -0800 (PST)
To: matthias.winter@betasystems.com, phil.hunt@yahoo.com, kelly.grizzle@sailpoint.com, morteza.ansari@cisco.com, erik.wahlstrom@nexusgroup.com, cmortimore@salesforce.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20251228153214.C7A25C000CD7@rfcpa.rfc-editor.org>
Date: Sun, 28 Dec 2025 07:32:14 -0800
Message-ID-Hash: A4YERHSZH5GDLIFROK57G3UTTNCRHCQN
X-Message-ID-Hash: A4YERHSZH5GDLIFROK57G3UTTNCRHCQN
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-scim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: debcooley1@gmail.com, iesg@ietf.org, scim@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [scim] [Errata Held for Document Update] RFC7644 (8367)
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/JRoVQUDnNKdSUuRDOawZdU6LFLw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Owner: <mailto:scim-owner@ietf.org>
List-Post: <mailto:scim@ietf.org>
List-Subscribe: <mailto:scim-join@ietf.org>
List-Unsubscribe: <mailto:scim-leave@ietf.org>

The following errata report has been held for document update 
for RFC7644, "System for Cross-domain Identity Management: Protocol". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid8367

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Matthias Winter <matthias.winter@betasystems.com>
Date Reported: 2025-04-01
Held by: Deb Cooley (IESG)

Section: 3.4.1

Original Text
-------------
3.4.1.  Retrieving a Known Resource

   To retrieve a known resource, clients send GET requests to the
   resource endpoint, e.g., "/Users/{id}", "/Groups/{id}", or
   "/Schemas/{id}", where "{id}" is a resource identifier (for example,
   the value of the "id" attribute).

Corrected Text
--------------
3.4.1.  Retrieving a Known Resource

   To retrieve a known resource, clients send GET requests to the
   resource endpoint, e.g., "/Users/{id}", "/Groups/{id}", or
   "/Schemas/{id}", where "{id}" is the value of the "id" attribute
   of the resource.

Notes
-----
The change clearifies that "{id}" is the value of the "id" attribute.

In the original text, the value of the "id" attribute is only mentioned as an example. It remains unclear if the value of the "id" attribute always is a "resource identifier" or if there may be exceptions. It also remains unclear, which other attribute values are considered "resource identifiers", e.g. the values of "externalId", "userName" for User resources, "name" for Resource Type resources, and so on.

RFC6743 specifies for example:
* "id" as "A unique identifier for a SCIM resource" (section 3.1)
* "externalId" as "identifier for the resource" (section 3.1)
* "userName" as "unique identifier for the user" (section 4.1.1)
But as a client I would rather not expect a GET call on "/Users/{userName}" or "/Users/{externalId}" to work. It is also unclear which object would be returned if the "{externalId}" or "{userName}" matches the "{id}" of a different user.

--------------------------------------
RFC7644 (draft-ietf-scim-api-19)
--------------------------------------
Title               : System for Cross-domain Identity Management: Protocol
Publication Date    : September 2015
Author(s)           : P. Hunt, Ed., K. Grizzle, M. Ansari, E. Wahlstroem, C. Mortimore
Category            : PROPOSED STANDARD
Source              : System for Cross-domain Identity Management
Stream              : IETF
Verifying Party     : IESG