Re: [scim] Call for support on proposed SCIM/SINS (re)charter

Phil Hunt <> Thu, 09 September 2021 01:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3EB143A1103 for <>; Wed, 8 Sep 2021 18:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 06nhUxw2UtqS for <>; Wed, 8 Sep 2021 18:34:01 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 35B043A1320 for <>; Wed, 8 Sep 2021 18:34:00 -0700 (PDT)
Received: by with SMTP id n34so320332pfv.7 for <>; Wed, 08 Sep 2021 18:34:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Wu4AuMUX0q6t+B/0swrap4XxB401j2Iiu451lD/j510=; b=GcS98ZIPauSYlqInGAWoLVPMjClJsp4RDqXsnQ/nLF+No3Sxn83mISm6uIBGZu8jqq J0DLzd7k99ZCehOUC//OTD7EgS6cELHTKOgAAFTfWut+ZY00H0Kaf1A23n/wqCQMGsif SSPfnxN2q/fP7CLYlCnVvAFRwgSqZm+yIQJmRzLjUMoDgLp5LE/iiV2VyhU871qIr6bF wjIJOsuinxzQHA/R9yLg1zY1XVawdMN7P/auCGmvccm/pw6T8LSQ05AZwODUZCkX2wb8 Oarxf1JgCpOwySUKGvA/H8/pVjWLDHvWyJHffUFJwVmD++2DxfODplUid6WAZDAdA0GN B9Sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Wu4AuMUX0q6t+B/0swrap4XxB401j2Iiu451lD/j510=; b=DIwSCvbusZjdUb6Km2WNiVjWnbrjIs3WUth8L3rWH310RFfxL++dpgdAqEAQlelf1J 999VzVSUuRwPwLM518i9UWDHJBGvCSm2aqAjre6kbPyq1wxlJ+Q4Nqv9QABl0zzUEK2l GSKcufw4slnIJeSZzKEZrVc1a+E+BnPoDGWinZZnlhTkvXF0giDihAP6e6LerZqzBp7S SncQyGj+gzDOLxO4MI4avu0fS21qs+53vikKPiWAo83LDepTUlsT0OzlfT7T3YzX+xWP lmgxSQcKVKxXQfpejZ+wQrYcCa3T/0bPTnDTBJkHRQ9jC8Y3F1lnXWOR/KQQUrbjHDg+ ik+g==
X-Gm-Message-State: AOAM530wGcSUX3366C4BLvM7tQsLBPLg/d0oj/0OM1Te/Mb7rpeiQDxB Gd3OAsr8SlkzeMfAwTXuVGxFB1G/355ABiE5
X-Google-Smtp-Source: ABdhPJx/tQ2x8zDB87Q2OHG6/1ha11HE0S2Weo5KbtUvFQWjwahMMc6Kdpi1EIpvXjgB1i11FgXfhQ==
X-Received: by 2002:a63:7d0f:: with SMTP id y15mr329064pgc.446.1631151239686; Wed, 08 Sep 2021 18:33:59 -0700 (PDT)
Received: from ( [2001:569:7a71:1d00:9503:1143:9e20:cec7]) by with ESMTPSA id d4sm139748pfv.21.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Sep 2021 18:33:59 -0700 (PDT)
From: Phil Hunt <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8E887732-5994-4BA7-9B63-2790A3922F2B"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.\))
Date: Wed, 8 Sep 2021 18:33:58 -0700
In-Reply-To: <>
Cc: "" <>
To: "Nancy Cam-Winget (ncamwing)" <>
References: <>
X-Mailer: Apple Mail (2.3654.
Archived-At: <>
Subject: Re: [scim] Call for support on proposed SCIM/SINS (re)charter
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Simple Cloud Identity Management BOF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 Sep 2021 01:34:07 -0000


Thanks for putting this together.

For this go around my interest lies mainly in Events and Synchronization and profiles.  I am willing to provide updated drafts for this process after some initial agreement on cases.  Drafts already in the archive (they may be fairly out of date!):

* SCIM Events - draft-hunt-idevent-scim <>  (needs to be updated to reflect the work we did in RFC8417)
* OpenId Connect Profile for SCIM -

Regarding the MV-Paging draft.  This draft has nothing to do with synchronization and is intended for clients who need to pull a limited number of values in a multi-valued-attribute in situations such as large groups. Most typical use would be in building a user interface allowing the searching of MVAs.

As far as exploring using paging as a synchronization approach is not something we should explore (ie in the charter). IMHO this appraoch an anti-pattern.  If its needed, I am happy to add text in the best practices or elsewhere as to why this isn’t a great approach from the perspective of security, DoS, timeliness, scale, and cost.

That said, a couple people indicated they wanted stateful paging. Unfortunately they didn’t elaborate on a use case.
Phil Hunt

> On Sep 8, 2021, at 5:21 PM, Nancy Cam-Winget (ncamwing) <> wrote:
> Hello SCIM participants,
> After some virtual meetings (thank you Pam for hosting these!) and discussion, there is a new proposed charter that addresses the points raised at the IETF 111 SINS session. 
> This is a call for support of the charter defined below, please provide your response by Sept. 24, 2021. 
> As you respond in support for the charter, please also specify if you are willing to produce, review and/or implement the resulting documents.
> Otherwise, do provide feedback in the time window if there are concerns or issues you see with the charter below:
> Charter
> The System for Cross-domain Identity Management (SCIM) specification is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier. SCIM was last published in 2015 and has seen growing adoption.
> One goal for this working group is to shepherd SCIM, currently RFC series 7642 <>, 7643 <>, 7644 <>, through the Internet Standard process. The group will deliver revised specifications for the SCIM requirements as Informational, and for the SCIM protocol and base schema suitable for consideration as a Standard. This work will be based upon the existing RFCs, errata and interoperabilty feedback, and incorporate current security and privacy best practices.
> In addition to revising the requirements, protocol and base schema RFCs, the group will also consider additional specifications as extensions to SCIM that have found broad adoption and are ready for standards track. This includes profiles and schemas for interoperability in additional scenarios. The working group will develop additional Proposed Standard RFCs based on outcomes of the following work:
> Revision of the informational RFC 7642 will:
> Focus on Use cases and implementation patterns
> Pull vs. Push based use cases
> Events and signals use cases
> Deletion use cases
> New use cases may be added to the revised RFC
> Revision of RFC 7643/44 will include:
> Profiling SCIM relationships with other identity-centric protocols such as OAuth 2.0, OpenID Connect, Shared Signals, and Fastfed
> Updates to the evolution of the externalid usage
> Document SCIM support for synchronization-related goals between domains focused on:
> Handling returning large result sets through paging, based on [draft-hunt-scim-mv-paging-00]
> Incremental approaches to synchronization
> Support for deletion-related goals including:
> Handling Deletes in SCIM Servers that don’t allow Deletes (Soft Deletes) - based on [draft-ansari-scim-soft-delete-00]
> Support for advanced automation scenarios such as:
> Discovery and negotiation of client credentials
> Attribute mapping
> Per-attribute schema negotiation
> Enhance the existing schema to support exchanging of HR, Enterprise group and privileged access management (using draft-grizzle-scim-pam <> as a base)
> Best, Nancy (as one of the BoF chairs)
> _______________________________________________
> scim mailing list
> <>
> <>