From nobody Thu Jun 20 08:26:15 2019 Return-Path: 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 650181200C1 for ; Thu, 20 Jun 2019 08:26:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=slack-corp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQIiTZCUfmng for ; Thu, 20 Jun 2019 08:26:10 -0700 (PDT) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FC6C120041 for ; Thu, 20 Jun 2019 08:26:10 -0700 (PDT) Received: by mail-qt1-x836.google.com with SMTP id x47so3542210qtk.11 for ; Thu, 20 Jun 2019 08:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=slack-corp.com; s=google; h=from:mime-version:subject:date:references:to:in-reply-to:message-id; bh=LIQXm1SwuGZyZaGrU3PEPQxUIjgJJLeevI2Y5JyVW1M=; b=ar89yU0KXSxfE1yjpDOQHP4Frw/W3gK3lVrxaNOsRHLCS0yxKMO1l+nAe+s/DqG9FK NRCvspScK5pR1H6FrhYi4V8Ecg1bIKl1VgyY9E2QulCN3px62PsmESx37fxvzeBw3H08 pD2RR+gICdgLf8TOekfwDzpnNUbCkGJUOk+lE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:date:references:to :in-reply-to:message-id; bh=LIQXm1SwuGZyZaGrU3PEPQxUIjgJJLeevI2Y5JyVW1M=; b=LGd9hcuczTqJBpMuLWYD4fs9lidbzS8htq8rpVscTzWkYnoZYcMKtS2GZKBGmX8WKg PYHGZvZAR/5rZ8GSUo5AgXzJSvxVFaYDFP4pNbIX5H8MPr3wylDoVd9h1z/ejcboYSy8 kOUwQ6WrG1YTCGdYdjHMH9fuhMhyV1vP0MoZD6QTMw9qyc5Jx2wKWcmPPMk5G8cUhwfs OYR3eJwmMMC+vGvk/WeGaCg0DozqxPLjP+NuFafIgylt1EEgvW3Aombpv+bHCnFNatUl FCGzJI7RxfyXd62Xuz0JAP9hr3t3HtUkcpzKbLcj97ithI3DIpWI0t5Yy0w6m0Kjd59x 6IfQ== X-Gm-Message-State: APjAAAX8sO0i1lepxZHGa9m07hrE/FqfwxThUhU5En0G06ZAbiG6Pfcs f7Ovr7Q/07z9KMSDe5Fo+wzBH5WzkLv93A== X-Google-Smtp-Source: APXvYqyyh71/NwerEYI2YBajSXExyFv3Ot8KzoHfik9f23sNnL0v/OyCQeHL93VOyuvnnCV57EiJfw== X-Received: by 2002:aed:3f0c:: with SMTP id p12mr47619432qtf.109.1561044368706; Thu, 20 Jun 2019 08:26:08 -0700 (PDT) Received: from [10.50.131.178] ([4.73.15.158]) by smtp.gmail.com with ESMTPSA id u7sm1027qtc.25.2019.06.20.08.26.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jun 2019 08:26:07 -0700 (PDT) From: Karen Nguyen Content-Type: multipart/alternative; boundary="Apple-Mail=_9AA13172-9BD6-41C1-9B9E-C4241993BEEF" Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Date: Thu, 20 Jun 2019 08:26:05 -0700 References: To: scim@ietf.org In-Reply-To: Message-Id: <60FB8AD7-F5E6-4585-8770-556C3C19F628@slack-corp.com> X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [scim] pagination for users in READ of single group GET /Groups/{id} X-BeenThere: scim@ietf.org 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, 20 Jun 2019 15:26:14 -0000 --Apple-Mail=_9AA13172-9BD6-41C1-9B9E-C4241993BEEF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi folks, I=E2=80=99d like to echo that we are also encountering scaling = challenges for the GET /Groups/{id} endpoint when the group contains = 50k+ users. We are considering leveraging the specification SCIM 2.0 section 3.4.2.4 = Pagination. =20 Would you recommend this, or do you have other guidance on what to do in = this case. Thanks, Karen Nguyen > On Mar 19, 2019, at 10:29 AM, scim-request@ietf.org wrote: >=20 > Send scim mailing list submissions to > scim@ietf.org >=20 > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/scim = > or, via email, send a message with subject or body 'help' to > scim-request@ietf.org >=20 > You can reach the person managing the list at > scim-owner@ietf.org >=20 > When replying, please edit your Subject line so it is more specific > than "Re: Contents of scim digest..." > Today's Topics: >=20 > 1. Help needed on READ of single group GET /Groups/{id} > (Ashok Dhakar) >=20 > From: Ashok Dhakar > > Subject: [scim] Help needed on READ of single group GET /Groups/{id} > Date: March 19, 2019 at 10:29:23 AM PDT > To: "scim@ietf.org " > >=20 >=20 > Hi Team, > =20 > The standard response defines the single group get result as > { > "schemas": ["urn:ietf:params:scim:schemas:core:2.0:Group"], > "id":"e9e30dba-f08f-4109-8486-d5c6a331660a", > "displayName": "Tour Guides", > "members":[ > { > "value": "2819c223-7f76-453a-919d-413861904646", > "$ref": = "https://example.com/v2/Users/2819c223-7f76-453a-919d-413861904646 = ", > "display": "Babs Jensen" > }, > { > "value": "902c246b-6245-4190-8e05-00816be7344a", > "$ref": = "https://example.com/v2/Users/902c246b-6245-4190-8e05-00816be7344a = ", > "display": "Mandy Pepperidge" > } > ], > "meta": { > "resourceType": "Group", > "created": "2010-01-23T04:56:22Z", > "lastModified": "2011-05-13T04:42:34Z", > "version": "W\/\"3694e05e9dff592\"", > "location": = "https://example.com/v2/Groups/e9e30dba-f08f-4109-8486-d5c6a331660a = " > } > } > =20 > In our case we have group with 50k members, so every time SCIM call is = being made to GET the group details by its /Groups/{Id} > We encounter performance problems as it ends up listing of all the = members every time. > The problem becomes worse when we try to list of groups and each group = contains 50k members. GET /Groups/{id}?count=3D20 > =20 > As of now we are circumventing the problem by specifying the = attributes as part of scim request = /Groups/{id}?attributes=3Did,displayName. > =20 > Every time we do 3rd party integration with SCIM compliant adapters = which is responsible for pushing the user information to our identity = solutions this becomes as bottleneck, > as it requires code changes. > =20 > I was thinking to address this in the following way > Show only few members as part of /Groups/{id} > Provide another endpoint to fetch members with pagination support = /Groups/{id}/members?count=3D100 > =20 > I would like to know any better solutions to this problem or work in = progress to address this so that I don=E2=80=99t implement the custom = solution. > =20 > Regards, > Ashok > =20 >=20 >=20 > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim = --Apple-Mail=_9AA13172-9BD6-41C1-9B9E-C4241993BEEF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = folks,

I=E2=80=99d = like to echo that we are also encountering scaling challenges for the = GET /Groups/{id} endpoint when the group contains 50k+ users.

We are considering = leveraging the specification SCIM 2.0 section 3.4.2.4 Pagination. =  

Would = you recommend this, or do you have other guidance on what to do in this = case.

Thanks,
Karen Nguyen

On Mar 19, 2019, at 10:29 AM, = scim-request@ietf.org wrote:

Send scim mailing list = submissions to
= scim@ietf.org

To subscribe or unsubscribe via = the World Wide Web, visit
= https://www.ietf.org/mailman/listinfo/scim
or, via email, send a message = with subject or body 'help' to
= scim-request@ietf.org

You can reach the person = managing the list at
= scim-owner@ietf.org

When replying, please edit your = Subject line so it is more specific
than "Re: Contents of scim digest..."
Today's Topics:

  1. Help needed on = READ of single group  GET /Groups/{id}
     (Ashok Dhakar)

From: Ashok Dhakar <adhakar@vmware.com>
Subject: [scim] Help needed on = READ of single group GET /Groups/{id}
Date: March 19, 2019 at 10:29:23 AM PDT
To: "scim@ietf.org" <scim@ietf.org>


Hi Team,
 
The standard response defines the single group get = result as
{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:Group"],
  "id":"e9e30dba-f08f-4109-8486-d5c6a331660a",
  "displayName": "Tour = Guides",
  "members":[
    {
      "value": "2819c223-7f76-453a-919d-413861904646",
      "display": "Babs = Jensen"
   = },
   = {
      "value": "902c246b-6245-4190-8e05-00816be7344a",
      "display": "Mandy = Pepperidge"
   = }
  = ],
  "meta": {
    "resourceType": "Group",
    "created": "2010-01-23T04:56:22Z",
    "lastModified": "2011-05-13T04:42:34Z",
    "version": "W\/\"3694e05e9dff592\"",
    "location": "https://example.com/v2/Groups/e9e30dba-f08f-4109-8486-d5c6a3316= 60a"
  = }
}
 
In our case we have group with 50k members, so = every time SCIM call is being made to GET the group details by its =  /Groups/{Id}
We = encounter performance problems as it ends up listing of all the members = every time.
The = problem becomes worse when we try to list of groups and each group = contains 50k members. GET /Groups/{id}?count=3D20
 
As of now we are = circumventing the problem by specifying the attributes as part of scim = request /Groups/{id}?attributes=3Did,displayName.
 
Every time we do 3rd party integration with SCIM = compliant adapters which is responsible for pushing the user information = to our identity solutions this becomes as bottleneck,
as it requires code = changes.
 
I was thinking to address = this in the following way
  1. Show only few members as part of /Groups/{id}
  2. Provide another endpoint to fetch members with = pagination support /Groups/{id}/members?count=3D100
 
I would like to know any = better solutions to this problem or work in progress to address this so = that I don=E2=80=99t implement the custom solution.
 
Regards,
Ashok
 


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

= --Apple-Mail=_9AA13172-9BD6-41C1-9B9E-C4241993BEEF-- From nobody Mon Jun 24 08:38:37 2019 Return-Path: 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 0BF171201A2 for ; Mon, 24 Jun 2019 08:38:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qLnXdws4HTv for ; Mon, 24 Jun 2019 08:38:33 -0700 (PDT) Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-dm3nam06on071b.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe56::71b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89882120150 for ; Mon, 24 Jun 2019 08:38:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Jz5FkA0oSc47u1UUnW7y3HcAdn74Hh1CUxCGdP5l8thfaXzoo+/tzRtQNdenEuIAu21mxrqb8+DybF847d5DCvDe+YzZN1qgmFx6ghCh8FkhjOejOXPvUmdZ22CmZZnXXCe2Xr8c7TqZdS5WC2oSNmsOjAFYjlTpLRcmdvirStyc2wnh5xtdtFBaM0AX4kwhouLAZRVIxRRSgkwo4xekVfXga0FKQ4GWBQskXSWeq2Ti1w8Xuy/C16zviz3ph53GBr/jtL52jtFj1uDZGK9xpaHpmvwwGl0LcqOBRsBZaTiWm27BExr13ZqUfM1x6gFYrQFAuiBC+XnkhqvXNGo1+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2MxELOUSYjGpvVCiT3LAMasAAOZNzJL7rIA6ANLYSjk=; b=dc5YWaisMdhIRn/7UKTH6G84ZC7PjR37fvcAeavHtipHNwYi99+9mYO6A6uPBx0DZykMf3ieN7AXmMg4MO+uE2mMZcriv/VQKqMFrBNi2+00oTlPFgiWjo9e1l/ekpHdiHcmqSnI6TcHjoo1Y5dp3IqtD6pJhFkhx7cvfb7mlUOhDLVKuNXMtjSKAGzPgv6TTBouQZWidiKmpcpENDHDFhouAkIaRtXjgFILWlgnwrpIj5BsvbRmWFPBEUCZeuzIyATdkcozLHgOsuu+VEBpEsz3aJnJXlcO5g++m31/l+kFXFH3ugi8sv7hH1QRaLlnEO2rsFB4AdG0C7sf58xQFQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=microsoft.com;dmarc=pass action=none header.from=microsoft.com;dkim=pass header.d=microsoft.com;arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2MxELOUSYjGpvVCiT3LAMasAAOZNzJL7rIA6ANLYSjk=; b=GOo6Qw0XGDHs1ZHZ3MRqKeUMIdw0lTJCXWm6spMFVf1kCPDAseR9erReI5AWsVFNuyyZPYYSdy4SVEDfULRVJtjkg1WUXcLSfLAhGSKTjBCT/5Rbx12ujzmJk8OjJDRC4P/LY9jjPNRVM068IIrrK4nNkG8mDaHf+ckjen6RyGI= Received: from DM6PR00MB0604.namprd00.prod.outlook.com (20.179.48.84) by DM6PR00MB0652.namprd00.prod.outlook.com (20.178.199.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2065.0; Mon, 24 Jun 2019 15:38:31 +0000 Received: from DM6PR00MB0604.namprd00.prod.outlook.com ([fe80::88fd:e828:bb5b:20b5]) by DM6PR00MB0604.namprd00.prod.outlook.com ([fe80::88fd:e828:bb5b:20b5%8]) with mapi id 15.20.2063.000; Mon, 24 Jun 2019 15:38:31 +0000 From: Mark Wahl To: "scim@ietf.org" CC: Mark Wahl Thread-Topic: FYI new individual submission draft-wahl-scim-profile-00 Thread-Index: AdUoWyMgjBRHPpDsQ/aYkrgQzy+x3g== Date: Mon, 24 Jun 2019 15:38:31 +0000 Message-ID: Reply-To: Mark Wahl Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=mwahl@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-06-24T15:38:29.9113447Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=3f9e39f8-040d-4c4c-95e6-d9b76cab2be9; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic authentication-results: spf=none (sender IP is ) smtp.mailfrom=Mark.Wahl@microsoft.com; x-originating-ip: [70.112.199.129] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 8136fd6d-7771-43dd-1f28-08d6f8ba0320 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:DM6PR00MB0652; x-ms-traffictypediagnostic: DM6PR00MB0652:|DM6PR00MB0652: x-ms-exchange-purlcount: 1 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 007814487B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(346002)(39860400002)(366004)(396003)(376002)(136003)(189003)(199004)(966005)(6436002)(22452003)(53936002)(1730700003)(5640700003)(81156014)(81166006)(14454004)(55016002)(54896002)(9686003)(74316002)(476003)(8676002)(72206003)(486006)(6306002)(236005)(7736002)(8936002)(2351001)(606006)(7696005)(316002)(66446008)(71190400001)(2501003)(6916009)(66574012)(86362001)(73956011)(66946007)(66476007)(66556008)(107886003)(76116006)(64756008)(71200400001)(68736007)(5660300002)(52536014)(478600001)(10290500003)(8990500004)(33656002)(256004)(14444005)(3846002)(6116002)(790700001)(4326008)(99286004)(43066004)(2906002)(3450700001)(102836004)(6506007)(25786009)(66066001)(10090500001)(26005)(186003)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR00MB0652; H:DM6PR00MB0604.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: lYbF6sqSX5M4NV4LygaAt4+9gLzeY6oMdP6c4AGU+pmyMFofJENqlA8W6ZdypjqlVA5COF+IUMcZn0HtjNVKH56ocoNsLdXDPm6QacAMzAEsWslbIsEqYF4U+DbxEFJQ0aJGQxNFUtb37ysILGsedWO3eVk8T2RX/KPhszB7Sv+2QiQzZHmoh8eOwJ2ws73PamOFrWr+3OFKPXjT1sTEeLsG11KILWpv6T6Tz34ovMmvicHIz2ENJHhgJ4ucon0fR76QhE8PlZNIP4kjp09JXajcmHlUNF2YOJU5BUFMDMRZEQkOgb7A2EO1aHqXuqFrLRYMum4xUiOFOy8FxNy3yUCSoTAQn7x20CAmKPdklfoWWcYBC0EMYR3/PQri1S1pxL5GgGE0nTY2oJ0gLrvbzo4jWKPqTaq3/DWDC8Ohkjk= Content-Type: multipart/alternative; boundary="_000_DM6PR00MB060474EFF71DBDC4D969160FE8E00DM6PR00MB0604namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8136fd6d-7771-43dd-1f28-08d6f8ba0320 X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jun 2019 15:38:31.8246 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: mwahl@ntdev.microsoft.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR00MB0652 Archived-At: Subject: [scim] FYI new individual submission draft-wahl-scim-profile-00 X-BeenThere: scim@ietf.org 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: Mon, 24 Jun 2019 15:38:36 -0000 --_000_DM6PR00MB060474EFF71DBDC4D969160FE8E00DM6PR00MB0604namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable A while ago I had written a draft for a profile of SCIM, for the use case o= f an identity provider sending updates about users and their attributes to = applications that were their federated relying parties. That draft expired= , but more recently, as interest in SCIM has increased, I've started to hea= r similar questions from app developers. Questions like: if they are addin= g a SCIM server into their app, what parts of the SCIM protocol do they nee= d to implement - are SCIM clients only going to be sending requests from a = subset of SCIM? Or, what is the minimum schema that their app needs to sup= port, does their app need to accept and store attributes that are part of t= he SCIM user schema but aren't relevant to the app's scenario? To start to= address those questions I've created a new Internet-Draft at https://tool= s.ietf.org/html/draft-wahl-scim-profile-00 to determine if there is interes= t in defining a profile of SCIM to help interoperability in this use case. Thanks, Mark Wahl Microsoft Corporation --_000_DM6PR00MB060474EFF71DBDC4D969160FE8E00DM6PR00MB0604namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

A while ago I had written a draft for a profile of S= CIM, for the use case of an identity provider sending updates about users a= nd their attributes to applications that were their federated relying parti= es.  That draft expired, but more recently, as interest in SCIM has increased, I've started to hear similar = questions from app developers.  Questions like: if they are adding a S= CIM server into their app, what parts of the SCIM protocol do they need to = implement - are SCIM clients only going to be sending requests from a subset of SCIM?  Or, what is the minimu= m schema that their app needs to support, does their app need to accept and= store attributes that are part of the SCIM user schema but aren't relevant= to the app's scenario?  To start to address those questions I've created a new Internet-Draft at  https://tools.i= etf.org/html/draft-wahl-scim-profile-00 to determine if there is intere= st in defining a profile of SCIM to help interoperability in this use case.

 

Thanks,

 =

Mark Wahl

Microsoft Corporation

 

--_000_DM6PR00MB060474EFF71DBDC4D969160FE8E00DM6PR00MB0604namp_--