Re: [scim] Request for Input

Kelly Grizzle <kelly.grizzle@sailpoint.com> Thu, 28 March 2013 13:10 UTC

Return-Path: <kelly.grizzle@sailpoint.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0B321F8C00 for <scim@ietfa.amsl.com>; Thu, 28 Mar 2013 06:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level:
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5+rL4QlPQzT for <scim@ietfa.amsl.com>; Thu, 28 Mar 2013 06:10:10 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe006.messaging.microsoft.com [216.32.180.189]) by ietfa.amsl.com (Postfix) with ESMTP id 0824021F8BF4 for <scim@ietf.org>; Thu, 28 Mar 2013 06:10:09 -0700 (PDT)
Received: from mail28-co1-R.bigfish.com (10.243.78.240) by CO1EHSOBE035.bigfish.com (10.243.66.100) with Microsoft SMTP Server id 14.1.225.23; Thu, 28 Mar 2013 13:10:09 +0000
Received: from mail28-co1 (localhost [127.0.0.1]) by mail28-co1-R.bigfish.com (Postfix) with ESMTP id 6DB224C043C; Thu, 28 Mar 2013 13:10:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:132.245.1.133; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0412HT002.namprd04.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(zz98dI9371I936eIc85fh1418I62a3Idb82hzz1f42h1fc6h1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL177df4h17326ah18c673h1954cbh18602eh8275bh8275dh1b8612mz31h2a8h668h839hd25hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1155h)
Received-SPF: softfail (mail28-co1: transitioning domain of sailpoint.com does not designate 132.245.1.133 as permitted sender) client-ip=132.245.1.133; envelope-from=kelly.grizzle@sailpoint.com; helo=BLUPRD0412HT002.namprd04.prod.outlook.com ; .outlook.com ;
Received: from mail28-co1 (localhost.localdomain [127.0.0.1]) by mail28-co1 (MessageSwitch) id 1364476208217904_2494; Thu, 28 Mar 2013 13:10:08 +0000 (UTC)
Received: from CO1EHSMHS004.bigfish.com (unknown [10.243.78.231]) by mail28-co1.bigfish.com (Postfix) with ESMTP id 32B1AB40050; Thu, 28 Mar 2013 13:10:08 +0000 (UTC)
Received: from BLUPRD0412HT002.namprd04.prod.outlook.com (132.245.1.133) by CO1EHSMHS004.bigfish.com (10.243.66.14) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 28 Mar 2013 13:10:06 +0000
Received: from BLUPRD0412MB643.namprd04.prod.outlook.com ([169.254.4.165]) by BLUPRD0412HT002.namprd04.prod.outlook.com ([10.255.214.163]) with mapi id 14.16.0275.006; Thu, 28 Mar 2013 13:10:01 +0000
From: Kelly Grizzle <kelly.grizzle@sailpoint.com>
To: Phil Hunt <phil.hunt@oracle.com>, Alexandre Santos <asantos@pingidentity.com>
Thread-Topic: [scim] Request for Input
Thread-Index: AQHOKz8MhibPsFuXXUSPark5DwFmRJi6OGKAgADaRtA=
Date: Thu, 28 Mar 2013 13:10:00 +0000
Message-ID: <56C3C758F9D6534CA3778EAA1E0C34375C3ADF35@BLUPRD0412MB643.namprd04.prod.outlook.com>
References: <CAPx6tN5PwV=hwifdCj3JiOKLsYCQZdewHOh7voau7OLSm3FWvg@mail.gmail.com> <AAE9F872-F35E-4A73-8674-4A7AF6C0537B@oracle.com>
In-Reply-To: <AAE9F872-F35E-4A73-8674-4A7AF6C0537B@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-vipre-scanned: 16F5D2E0003FE016F5D42D
x-originating-ip: [72.182.10.254]
Content-Type: multipart/alternative; boundary="_000_56C3C758F9D6534CA3778EAA1E0C34375C3ADF35BLUPRD0412MB643_"
MIME-Version: 1.0
X-OriginatorOrg: sailpoint.com
Cc: "scim@ietf.org" <scim@ietf.org>
Subject: Re: [scim] Request for Input
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/scim>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Mar 2013 13:10:12 -0000

PATCH was added specifically to address the "changing membership of a large group" use case.  The POST/DELETE to the members endpoint was considered when looking into PATCH, but unfortunately this does not work in the general case.  Specifically, this only works if the list elements have a unique identifier, so it fell apart when trying to apply this to adding/removing addresses (which do not have a unique identifier).

I'm not convinced that we need to add another mechanism to solve this use case, but I do agree that PATCH could be simplified.

--Kelly

From: scim-bounces@ietf.org [mailto:scim-bounces@ietf.org] On Behalf Of Phil Hunt
Sent: Wednesday, March 27, 2013 7:02 PM
To: Alexandre Santos
Cc: scim@ietf.org
Subject: Re: [scim] Request for Input

I think this may fit in with our discussion of adjusting PATCH to work better with multi-value and complex attributes (ticket 18).

So far, we've been avoiding extended paths that go within the Resource entity (e.g. to address specific attributes).

If you were to do the item below, I think you would have to add the attribute name to the path at the very least.

PUT /Groups/<groupid>/members/Users/<userid>

Still I think that may have problems if the member is actual a URL rather then a simple UUID.

Phil

@independentid
www.independentid.com<http://www.independentid.com>
phil.hunt@oracle.com<mailto:phil.hunt@oracle.com>




On 2013-03-27, at 4:01 PM, Alexandre Santos wrote:


For groups with many users (>10k) it becomes problematic to do POSTs or PUTs. The only alternative would be PATCH. However PATCH is not mandatory.

For this reason we would like to request your input for the following proposal: allow membership changes via PUT and DELETE.

For this the PUT and DELETE commands would be in the format:
PUT /Groups/<groupId>/user/<userId> - to add a user to a group
DELETE /Groups/<groupId>/user/<userId> - to remove the user from the group

Thank you,

Alexandre Santos  | Sr. Development Engineer
PingIdentity  |   www.pingidentity.com<http://www.pingidentity.com/>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
O: 604.697.7056
Email: asantos@pingidentity.com<mailto:asantos@pingidentity.com>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Connect with Ping
Twitter: @pingidentity
LinkedIn Group: Ping's Identity Cloud
Facebook.com/pingidentitypage<http://Facebook.com/pingidentitypage>



_______________________________________________
scim mailing list
scim@ietf.org<mailto:scim@ietf.org>
https://www.ietf.org/mailman/listinfo/scim