Re: [scim] New charter - strawman draft

Quint Daenen <> Tue, 16 June 2020 19:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EBB293A125C for <>; Tue, 16 Jun 2020 12:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 N7ZKSCFlD2zm for <>; Tue, 16 Jun 2020 12:08:41 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CB6193A1255 for <>; Tue, 16 Jun 2020 12:08:40 -0700 (PDT)
Received: by with SMTP id n24so22856184ejd.0 for <>; Tue, 16 Jun 2020 12:08:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=HsKn6PUmxrzWl1u3AHY7WSUXmJZ612OrOC1IGya7t78=; b=LAcZbxMdrDK24Bf3aEatAkjf6e4bX6MoqiDsM+5kz8/Ldn7L4tdZnx/4awku5tl6Wc TwpThkZ2deRVn4bGkesgmpXybUPL925rboMCjr0D6ahvWXS8g6NrEj9GZKLcpBAsBme9 ggsY3mP1ofAgJA0J/c/fdk2DKGdapxYHmvB6oHYKY08Mwb2MvqteSb/Qr5rpM00e1jrn ptJk2vTl8o593i+NT2S8Pv4iScX0DC70Sq1YV4kFjhizVtp6ghbD64UR4iJdS2w81qSw fP+/rtrDzQAbKC6i1d6UrQHVm/D5twz0l+mae0v5Fausy2YJJxJCcjKmQ4qgg9B+l2JN YfJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language; bh=HsKn6PUmxrzWl1u3AHY7WSUXmJZ612OrOC1IGya7t78=; b=YPIo0YX9H6OnBOVs89TfqL858E/9JGh+X97M6Z+0s05YFtGrFLTreFtD2bF+f9XLqo Zr6yx6aeJWwLpttEdbw8QW4qolb+p/tcUWJJ8gMvRR023OzUVIoRIt9zgjEzzUr8e4Q6 u5Pq4g5VthIZLwRN6WMI2vEd2zS97oN9QktH7eLYcvvb2KxnfWV5CisurZTIjU06e+MA 8VcCbAcYQb0z9a/tp5VcL2Or4ATb4GSPxCZ3YrC8Qf+6YF9PSqn+SN+rozzm76Ri4lzn V33KTz3CZeTrJ+ELtvieWDOMeR8ALWQROSbI3yUJmncK5b6ftc9ypVg17CsjX/Q915p+ efZw==
X-Gm-Message-State: AOAM532Zl66qyjcjemEMzx8dpVtt0GIaVLNtiVZp3pUhewMZXrRUibXe DFJ+6pYAvUU+UVQX44I57lA2Z52fE3I=
X-Google-Smtp-Source: ABdhPJy4nYho3nx9I6Pl+BCfPz4oFEbkZsW86n94BbNkwvOEluxG2Iyx2qJ0q8OpY65s2U6AWEE9Ig==
X-Received: by 2002:a17:906:ca0e:: with SMTP id jt14mr4014586ejb.325.1592334518702; Tue, 16 Jun 2020 12:08:38 -0700 (PDT)
Received: from ?IPv6:2a02:1811:c8e:4300:b953:6d9:b4e8:fcc2? ( [2a02:1811:c8e:4300:b953:6d9:b4e8:fcc2]) by with ESMTPSA id lw11sm11456660ejb.58.2020. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jun 2020 12:08:38 -0700 (PDT)
To: Darran Rolls <>, "" <>
References: <>
From: Quint Daenen <>
Organization: Elimity
Message-ID: <>
Date: Tue, 16 Jun 2020 21:08:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------17DBF5428868C6500F2BD98F"
Content-Language: en-US
Archived-At: <>
Subject: Re: [scim] New charter - strawman draft
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: Tue, 16 Jun 2020 19:08:43 -0000

Hi Darran

Thank you for writing out this draft proposal and starting up a discussion.
See you on Thursday 25th.

Quint Daenen
LinkedIn <> | GitHub 

On 15.06.20 14:11, Darran Rolls wrote:
> In readiness for our interest group call on Thursday at 11am central 
> US time, I wanted to throw out a strawman charter statement.  Please 
> review and comment here first:
> The System for Cross-domain Identity Management (SCIM) working group 
> is being re-chartered to extend the current SCIM 2.0 specification, 
> further refine its operational capabilities, and enhance the 
> standardization of methods for creating, reading, searching, 
> modifying, and deleting user identities and identity-related objects 
> across
> administrative domains.  The goal of this renewed effort is to further 
> the operational simplification of an expanded set of common tasks 
> related to user identity management in services and applications in a 
> growing ecosystem.
> The word "Standardize" does not mean that the working group will 
> develop new technologies.  Specifically this working group with look 
> to build upon the existing SCIM 2.0 specification rather than defining 
> any new protocol elements. The groups new work will be focused on 
> delivering operational protocol enhancements and extending the schema 
> definitions to cover more managed objects and endpoints.  To better 
> support the growing number of commercial and open source 
> implementations of SCIM 2.0, this effort will also focus on delivering 
> new capabilities targeted at  promoting interoperability and enabling 
> the verification and testing of different implementations.
> The SCIM working group will initially be directed towards operational 
> protocol enhancements and new schema definitions in the following areas:
>   * Multi-value paging & cursor pagination
>   * Relying party user provisioning
>   * Soft Delete
>   * Extended HR /user data and related action events
>   * Ratification of extensions to address Privilege Account Management
>     user cases
> It will follow this work by considering extensions to the protocol and 
> operational model that address the verification the establishment and 
> interoperability between implementations.  When and where necessary, 
> the group will modify and enhance the existing SCIM 2.0 schema and 
> REST-based protocol, but will do so with a focus on backwards 
> compatibility and the goal of adding to rather than breaking an 
> existing SCIM 2.0 implementation.  However, where enhanced 
> interoperability and streamlined operations are necessary, changes may 
> be specified that require updates to an implementation to remain 
> interoperable with this new work.
> Finally, the working group will continue to ensure that the SCIM 
> protocol embodies good security practices. Given both the sensitivity 
> of the information being conveyed in SCIM messages and the regulatory 
> requirements regarding the privacy of personally identifiable 
> information, the working group will continue to pay particular 
> attention to issues around authorization, authenticity, and privacy 
> and consider new features targeted at enhanced security for the protocol.
> -- 
> Darran Rolls
> LinkedIn <> @djrolls 
> <>
> _______________________________________________
> scim mailing list