
From nobody Wed Aug  4 07:00:39 2021
Return-Path: <Pamela.Dingle@microsoft.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 F12E13A170C for <scim@ietfa.amsl.com>; Wed,  4 Aug 2021 07:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01] 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 dcs_eDvI7Yrq for <scim@ietfa.amsl.com>; Wed,  4 Aug 2021 07:00:34 -0700 (PDT)
Received: from outbound.mail.eo.outlook.com (mail-oln040093003008.outbound.protection.outlook.com [40.93.3.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDEA33A16F9 for <scim@ietf.org>; Wed,  4 Aug 2021 07:00:33 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=afBDQkeFp5LU9ujOgKNghoHfFj1jZexzOzdc2WWpQ8E0R1rSAdaHrIuu5eYl/axb7ZqkjAsDvyfD/C2zSYWWmaZpjcUTIPKqxtifaIb3nB04PT5inv/vsdrlL6ZSGX/SzokRRSseUqRpvVAN7fzhnb/GvxiMLqD1yk1xy+GPA4DI8BqQN1Rrep3/2w3YNhQfsh6YZeYZJtzUHZCy5hzdnege7pbo81qo6P05dJ06fhOKXCmBm2oLPhFNktSKe6U+t7YEJxX0JPSyBg7FQQpbv8DG8vQaz1eqJ1w8PjK1AImhyRanuLJmTxCvj0hKFr9gAfGgln2qTIw2t/VWTNTpWA==
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=0+qk7SdkeUp5iuqwW3D0bKXKWXqWYT4Fm6VG4K/jqHA=; b=PbCR1ZR38Q66LfgY+/oPoSEIa7SYuF7vt97Pdten55SaaJV7VY0K2XtEG4EPGBpEZ3/vVbcHV2emJ+IFCkyU19viSgRpJ60cFtuVW5eDxu8fcdypNt5UPEPfxPqmRPvwsAHu9vZs4GdBusp0gJqH/KQzbJNIQDq0Q2sh/0RzPGXtVktXTvKX2TP+6oNvl70CGI6Vh/R6CUhAVYTpxIJttEhRa4rTIYSjTHVhTHwixGb0ImeqvBTo1jekysJdvJuzm/YVmuRtz9jlhT6Nq7Z6hs6M72WKCN4er49skK0Hxm0NO4u+2Icu/DhteQ7kdZ/GgUfYWp0QrUoCgU1O+x8PjA==
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=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0+qk7SdkeUp5iuqwW3D0bKXKWXqWYT4Fm6VG4K/jqHA=; b=B3aYCnAf0/3jjWw67P9SgxwVQQbTwhGhUN+QMb0rlvU8f7wrfCoFmjezL/Htw/Q5bWzQA6Try103Oof3ReBGG1lUdt7EJTdnLegTtqZRgvCgZSpPNlnSo4HVsNPfD0C7k0AVM7XWj2ggoQGgxLArFQKz5S63wXnxbshLBBil7Zw=
Received: from BY5PR00MB0760.namprd00.prod.outlook.com (2603:10b6:a03:1d1::21) by BY5PR00MB0674.namprd00.prod.outlook.com (2603:10b6:a03:204::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4433.0; Wed, 4 Aug 2021 14:00:29 +0000
Received: from BY5PR00MB0760.namprd00.prod.outlook.com ([fe80::e5bc:3acd:5177:11e0]) by BY5PR00MB0760.namprd00.prod.outlook.com ([fe80::e5bc:3acd:5177:11e0%9]) with mapi id 15.20.4433.000; Wed, 4 Aug 2021 14:00:29 +0000
From: Pamela Dingle <Pamela.Dingle@microsoft.com>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: SCIM IG meeting in one hour (8am PT)
Thread-Index: AQHXiTeBGfBA7NmHuUKTyoYchHrMYg==
Date: Wed, 4 Aug 2021 14:00:29 +0000
Message-ID: <BY5PR00MB07602ADB88270A9C6102F3F6F6F19@BY5PR00MB0760.namprd00.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3d92c4d7-bb3d-41ba-bf62-08d9575037c0
x-ms-traffictypediagnostic: BY5PR00MB0674:
x-microsoft-antispam-prvs: <BY5PR00MB0674080361F8B711D1EAF15FF6F19@BY5PR00MB0674.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: h/nY0to7bZwhNaC2J5ONLl/CxVhd8bASObonF8nwUIRJOotXSL+iI+qrKfFRex375wyvl53JQCqX55HXaYdWTTqOcF/54HfueXyxX4C/ch6ePi06y/ewGQDeqLxAtbU/N9CNkpBwSSxv8+e3+iFPoAyPZX3zLy1FIseC45ab41truZ6e7ulq1cZNM8YsI/8xvKm1Ipn6S3P0rIU/sdyg2TZgpXyT0xJv1keQsGm1EsCRpYg5YqWU9WGzrYQOk2nv/y2QLDXuiK6NCGERIKsm0vyQJWGAJ3+ipErPIivNV3DxYTcffqyRA5+oVwA3Lr4zyLhtqxQPZD4QrKXOVNxlj0b34Br5YWNWgA5+dMVjKoS0UEM01TIWxy+3doA8EVzpD7x1g/8j1QEoq+oH4hjELGAjDcObqhjCYl1a1UH/ildaZC/CwoDcvuj5x6WIFHmFw0nyKLgoJem3JyeXV/0mearSYvhJMtJftwm139G56p/FwZGRVXK91M2qGjp4siaEjYdFQFc3FtJmI+EXW9GOm6k4muEj8Ub/L0s36xDGMj7Hswyz2xE2oQ1gCSH4AosQw2fy0cQW2WwPVtMzCoRL0YsVRV4h3L7WNi/3OB4oKSy0LFveORbyV/r15Qo+/FsN8QAq5fcN2Du4jG3a4od1A3odRmW0VWZPIbqOp4mQo1NEOQu1rqWs87d57tXlX9b7AGx2m5DGWzSLQJfvhQIGoxphhn4Sluo2M+qH5vI1ff1nGkY7zH5jOxj4xlAtVfFxtsvicl4GEIU1NOjHeqZhyXq4eTCFFpdPrRtTOW2dM+CECqtzglac99jjx1RXgzkLcyyit3wUGrFKueTZgpX/Aw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BY5PR00MB0760.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(66556008)(186003)(316002)(66946007)(26005)(2906002)(64756008)(166002)(5660300002)(55016002)(6916009)(66446008)(8676002)(83380400001)(66476007)(76116006)(8990500004)(8936002)(52536014)(9686003)(19627405001)(10290500003)(33656002)(7696005)(86362001)(38100700002)(966005)(71200400001)(82950400001)(82960400001)(508600001)(122000001)(38070700005)(6506007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?pAcojhu3icgSa2uQfLyWId0BWTP+8SORyRK0k3nxL5JXKTfsPGpLtKznwb?= =?iso-8859-1?Q?Cr2z84yTjKnT6Z3QlQ+0RhCCtXTqsHOwRsQnUfcjeVYxUwAJktd54hPaX0?= =?iso-8859-1?Q?0x/Ky88a2yy8k6ZwNyC/gbg9BXVZgp8/Nq96os0/idC3/d9KjKH9SMuuqD?= =?iso-8859-1?Q?V8WbD+hpDpXW8dowVMGri4B+LsJNALT8X1eazMuK34ExDZGuWWqby0Xi/M?= =?iso-8859-1?Q?mPhlidTLrCdd7vkRkg6SyUT9Te82OcAr1DFjORFW/8EvuqyjXlXmw9Rhrn?= =?iso-8859-1?Q?KkSYD5ITu/upBwu+iYCnurofxfcWnEHC37sGVC5Zcm0QUzYR75otUveIn1?= =?iso-8859-1?Q?Gk/COSrcY0tq4vuKfC1m+CRk1zuD3BbPeEIyak+cKKyP4RTV68xdmujcPe?= =?iso-8859-1?Q?zcb9e4c2FByEmWYnqOIGlwuwYK+7d/bNv/THeF+IlcfOYfrVwF0AN/mhWb?= =?iso-8859-1?Q?ZTAIFDyt/UeeHTXgZ2Rw4akh3y5E27RwoLeWqlkep6T7vlCIJCFeFWiSXo?= =?iso-8859-1?Q?zqaniIXV27Okz9pOiYEYnFPFX2nLhvvFRL1/E3LDNZCeAcfGhxJu+kbQP0?= =?iso-8859-1?Q?SJjhZwNzCOie6mXMGVBGdnRCcODpiX/oNlK7GuQ+jMihTRs/91bx/EGdVH?= =?iso-8859-1?Q?jZ02R0ZTamEKCTha+7Xt7pzOxjkc3XYYaMLpJufEvs30xPCcdM1ejklBpl?= =?iso-8859-1?Q?mUxrbpS0UExdIUEEWhGApdszbHXuFR3Xdb5oFe3xMqJQ/dsSyPVqImYU/Q?= =?iso-8859-1?Q?pfvnDd7M9jmF8QyNmptWeOmtpJLR6B3pAXK8BzjgNSYW3UT4TPhitltst/?= =?iso-8859-1?Q?7q0bbVhBrcuUrdonybTEWiJ0ugSBdGf8yqTmOu7e+pvIrFFuUeTRWpB+Vo?= =?iso-8859-1?Q?6M8pd8JjTgUi7mcTsJmAqfGb0vjdeG6Q7A5NH5e0ZfWb1RgCXxZxS0NMfm?= =?iso-8859-1?Q?0RxiL+qShBFeY+KuG6d7ZM5exGq4Vy3jk7I5EQbrmDY8qCYMthPPh+xmls?= =?iso-8859-1?Q?qsbRpCS9y1O4oHNYmmuO84Fk4CwVnbLWfOxSamucNKdbGXD8WK368fski1?= =?iso-8859-1?Q?hXNg/MCWU2g9iI+psVYGwcLGrJML6npei28P78Fet6KGet29++O3IZwrOV?= =?iso-8859-1?Q?XTmJvE/D9iWjDPpTIlKbmlcUPvnF5jAjrvkIbxxUoMAMh9H/tXJs41W7k7?= =?iso-8859-1?Q?etRpzMg5dmNElQSPQOnOtWeUoW7dtwwrtlLITZbcjXpmhjm/ESpSuY7v+3?= =?iso-8859-1?Q?VnAQjnVV+/npRIg0gYbvTzzYiv9nisCIZZX2Qk+B3/sYu9/H5BhhihSuIW?= =?iso-8859-1?Q?zCKr0uWCeWnAY08HWfet95iW26ydpAwYmX8tUm1L5f4pl2VdgfYwnYgwXk?= =?iso-8859-1?Q?OJv/WZNBMQ?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR00MB07602ADB88270A9C6102F3F6F6F19BY5PR00MB0760namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR00MB0760.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3d92c4d7-bb3d-41ba-bf62-08d9575037c0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2021 14:00:29.2899 (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: o/8mq4YUwwOx685zT5PjYdSeaHHDz4Qzc1lrXf//TMqmyG+lEyqNfkca8P2IwcprUR7kuvYaReyxpJIUC0AWuw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR00MB0674
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/ThsZ6ri2MDXiXGcJZTG7-t9uXMU>
Subject: [scim] SCIM IG meeting in one hour (8am PT)
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 04 Aug 2021 14:00:38 -0000

--_000_BY5PR00MB07602ADB88270A9C6102F3F6F6F19BY5PR00MB0760namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

In today's SCIM IG meeting we will talk about the SCIM BoF meeting last wee=
k - what went well, what was unexpected and most importantly what we need t=
o do next.   We will put a summary into the list right after.  The BoF meet=
ing was recorded: official IETF 111 recording of the BoF<https://www.youtub=
e.com/watch?v=3DrxpaaU4Tijo> for anyone who was unable to attend.   We had =
strong attendance at the meeting, and I believe we are now at a point where=
 we can take the feedback from that meeting and any concerns or feedback fr=
om this list and tune our charter to move towards a WG.

One thing we know we need are thoughts and reactions from those of you who =
have not been in the SCIM IG meetings.  If you can make it today, we hope t=
o see you but if not, your thoughts on the list are both welcome and critic=
al to our success.

Today's meeting link is below, or you can add the recurring meetings throug=
h the IG group's .ics calendar feed on the github site<https://github.com/S=
CIM-Interest-Group/wiki>:

https://teams.microsoft.com/l/meetup-join/19%3ameeting_MmRhN2UzY2ItODZkZi00=
ZDZjLWI3MTItODlmMjc1NmFjNjEw%40thread.v2/0?context=3D%7b%22Tid%22%3a%2272f9=
88bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%2285bc2986-6412-41c0-ab6=
d-98c80048fe64%22%7d

Cheers!

Pam


--_000_BY5PR00MB07602ADB88270A9C6102F3F6F6F19BY5PR00MB0760namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Hi all,</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
In today's SCIM IG meeting we will talk about the SCIM BoF meeting last wee=
k - what went well, what was unexpected and most importantly what we need t=
o do next.&nbsp; &nbsp;We will put a summary into the list right after.&nbs=
p; The BoF meeting was recorded:&nbsp;<a href=3D"https://www.youtube.com/wa=
tch?v=3DrxpaaU4Tijo" title=3D"https://www.youtube.com/watch?v=3DrxpaaU4Tijo=
">official
 IETF 111 recording of the BoF</a> for anyone who was unable to attend.&nbs=
p; &nbsp;We had strong attendance at the meeting, and I believe we are now =
at a point where we can take the feedback from that meeting and any concern=
s or feedback from this list and tune our
 charter to move towards a WG.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
One thing we know we need are thoughts and reactions from those of you who =
have not been in the SCIM IG meetings.&nbsp; If you can make it today, we h=
ope to see you but if not, your thoughts on the list are both welcome and c=
ritical to our success.&nbsp;&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Today's meeting link is below, or you can add the recurring meetings throug=
h the<a href=3D"https://github.com/SCIM-Interest-Group/wiki" title=3D"https=
://github.com/SCIM-Interest-Group/wiki"> IG group's .ics calendar feed on t=
he github site</a>:&nbsp;&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<a href=3D"https://teams.microsoft.com/l/meetup-join/19%3ameeting_MmRhN2UzY=
2ItODZkZi00ZDZjLWI3MTItODlmMjc1NmFjNjEw%40thread.v2/0?context=3D%7b%22Tid%2=
2%3a%2272f988bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%2285bc2986-64=
12-41c0-ab6d-98c80048fe64%22%7d" id=3D"LPlnk">https://teams.microsoft.com/l=
/meetup-join/19%3ameeting_MmRhN2UzY2ItODZkZi00ZDZjLWI3MTItODlmMjc1NmFjNjEw%=
40thread.v2/0?context=3D%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011d=
b47%22%2c%22Oid%22%3a%2285bc2986-6412-41c0-ab6d-98c80048fe64%22%7d</a><br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Cheers!&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
Pam</div>
<div class=3D"_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_=
1"></div>
<br>
</body>
</html>

--_000_BY5PR00MB07602ADB88270A9C6102F3F6F6F19BY5PR00MB0760namp_--


From nobody Fri Aug 13 05:36:27 2021
Return-Path: <Pamela.Dingle@microsoft.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 094623A16F8 for <scim@ietfa.amsl.com>; Fri, 13 Aug 2021 05:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=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 yrUgvqqbm7wz for <scim@ietfa.amsl.com>; Fri, 13 Aug 2021 05:36:19 -0700 (PDT)
Received: from outbound.mail.eo.outlook.com (mail-oln040093003008.outbound.protection.outlook.com [40.93.3.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F2F3A16F6 for <scim@ietf.org>; Fri, 13 Aug 2021 05:36:19 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Nf9Q8dO/p5+iYvU1ud5Yq9+o30Dj7Zord6imkuo+3VYpTL+gBIyj4SJi0MWM5EPZ6xw7jWnLVySpLCa7dvDyInXn8osXC6zII5r834PxHvCMiYfksAEFJIElvw47ZYLOhAxScHcW3nIeN6Mml74bMsUxN/uYFfXxpz2D6dECblThGS7gkI0HZVIpmyKyEuvgEHLYsUY3N6fThg4FSG955qxs2toCJPdBel/O706lQS1G+eTEuJd52hwdNjWgqFnjK6/QwDci1m3mcDjyu+rwwbxe4afc+AWBaVWG09eUfQwyQfp/XqT7gS5owDcJqzER6PNa/cVcLGf0WK602hQ9aA==
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=CMn57HeV7GAE/91bKWd9SIfpTebtuHXQHgAZtpNwrMI=; b=dynz4KGf8ZKqr14C/ew34vIuKcFb28JPEqxBBImuOtjxDyItC3zP/61qQzA9xyH+u3pSlLLd5ss4HfOsnKyAxJvD/lmknejuESwmHxvh9ob+htll9E+PHy+K+1kgOioC6ituXtFoebifE7BGOYdMYQRbxqPADQtrmf+7RxZvvx7UG45BiT8reQGT4BC3EA3jrDa1Mpmj8Hnwkr1bb8ZWa/z1egvjSaB7Q81m6A2yh/40a4kkRNqnO6iRJ8KUyPX3f/gZ0f86A3ZDSmxSh0LW9w1QztcNAkLA1TlgXDZsXWUosfYa5ZY3a9+1UQKpH4TF7N6j5V/5zAie56zNkH+R/A==
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=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CMn57HeV7GAE/91bKWd9SIfpTebtuHXQHgAZtpNwrMI=; b=W8UEySzLtkeaHQSePnMtKP8kEijv04t1DDBQtK6Ekar4gaBOysCC9veFibcnEuFqMOIcijQrawz/C3UnUgwWRT9d8DiIOmn24rJQEyk/PdS5vpZzQJz7LGkMgWkqkSmD/NkA1iCyswu8ddrll4jWh6JCEtB4NuXkemb+cvhOSjo=
Received: from BY5PR00MB0760.namprd00.prod.outlook.com (2603:10b6:a03:1d1::21) by BYAPR00MB0632.namprd00.prod.outlook.com (2603:10b6:a03:106::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4456.0; Fri, 13 Aug 2021 12:36:11 +0000
Received: from BY5PR00MB0760.namprd00.prod.outlook.com ([fe80::b1ed:f81d:e8ca:9e46]) by BY5PR00MB0760.namprd00.prod.outlook.com ([fe80::b1ed:f81d:e8ca:9e46%8]) with mapi id 15.20.4460.000; Fri, 13 Aug 2021 12:36:10 +0000
From: Pamela Dingle <Pamela.Dingle@microsoft.com>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: BoF Review and workshopping the Charter  based on SCIM IG call,  Aug 4
Thread-Index: AQHXkD59zrEiCh3RDEuUBvNOedb2qg==
Date: Fri, 13 Aug 2021 12:36:10 +0000
Message-ID: <BY5PR00MB07605CD725FD313DCE5BD78AF6FA9@BY5PR00MB0760.namprd00.prod.outlook.com>
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_SetDate=2021-08-13T12:36:11.837Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 121d25c6-376f-4c5f-04bc-08d95e56ee5e
x-ms-traffictypediagnostic: BYAPR00MB0632:
x-microsoft-antispam-prvs: <BYAPR00MB06322DABC4391180A37E4CE7F6FA9@BYAPR00MB0632.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /xunC84IMTwwL9YkCX2U6y5ftBu6N0Fix7ddV1X2Qc6YQ0cfvxiGL1a8UGQJEcnYDAzP4TOB3+opVp/x4ygEYOfUg6x2xMuIJJXQW/3rH2sm0JJgwMmLO1sMiE2USC4ncSB1XBL/5xfjE39TLJxpy/Pr34Tf33zrGAHhcIKFrZ4dcNwT756ALwuEqYzB6rwGO8S8H//gn7Ehmg3CyrI7Cdv1tAn8wKOYHlwYO75GvzjFlPxWTSmTm/DAJ/SyeVky8CQ6jExWWPIBwRGsFrpCU/ic9Dly9WDbyRuB7VI7XR4b9gvdwpqSOZfRwn3EV3POL8uiQlvqZONRr+Mz57+rqjcF1W0M1h84K0rlh/+xE0FGCJxNfJUB8de7Oa+nUTfXZunQzgwnFGRm9S3xHza5xg9ejjusGEfc88h/UIhbPGWuTCVmltrevTqnikJnFCrhnLCYX+5reuAmpEs7KKde0AeH2jw/GE/GUjOKXvt8FVEsc/xat8jQxbD/2hh6fyNNYd+G1BWMGWv87xUX51dgcXFoxcwvxUa+kpYRYg76tVTvCDssl/9ImJDYcK3sAoUNzoIrEiyzYr6nUmB9dehvIQFLzdiHq9kVzPHkiiP1r3azqqWBuSRsLCNUIhWD5Y14NqbKhYTIEhzZzZrDZnIi7xsJoPz9Y0h3TRHQxWOVgGnwPP1zT77l8eXeTVTiy5PbQKBKmJjOueYJfviGA/LyntOoiRhjk5ekPjt2FmnGMOLLm2uCA+ihtQEdseQZhKpyTk+pg+jxBP4vwt0k78wtmZTNYIhUaN+gzEUq2Y9Lo8t0SLspC4o6tLWiw+eOiweQZGPOeYY33UdyKp0sMzUDOQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BY5PR00MB0760.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(19627405001)(7696005)(2906002)(122000001)(38070700005)(186003)(26005)(38100700002)(66556008)(508600001)(8676002)(8936002)(33656002)(6506007)(9686003)(83380400001)(5660300002)(82950400001)(966005)(66946007)(52536014)(55016002)(82960400001)(86362001)(10290500003)(8990500004)(316002)(6916009)(64756008)(166002)(76116006)(66476007)(66446008)(71200400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?lkIZAt0QGMOjHYxWphFyu/BC+VgHixorTkiJ620qREKRAKhkSaDHlTN+TZ?= =?iso-8859-1?Q?QxQHUDOklA6ituCqvA1l56l4o8d/tciAxqpwskwNWT7wF47in2o6sm9igo?= =?iso-8859-1?Q?WLY9EpSwPJkwCYutgQIj6JpIn5OERP+DC/nBmFgSXXRPPq9dZJTzbusikn?= =?iso-8859-1?Q?Saf7bLKbpLonDbN0/nALYgw7IOv+mMI5fmuA3ytFobGPPEhOyr/sJWPz0D?= =?iso-8859-1?Q?Bb03zKy7LT8XRGHKH8ORfG/l4NSV8tRULnwpSKC/YO6VhcNAjGkWvxA2eY?= =?iso-8859-1?Q?jWEBZn5xO2zDmJlC0ZWIR5hnysJvuDkhu/QGET9NLotVbudNbRGhmHYuMh?= =?iso-8859-1?Q?Z3DYizORwhoTWCcCqVcmCOrzwrWDMWPKNBNsUGdFqGi3bUykiAMPqzjjVE?= =?iso-8859-1?Q?a88VQqq1xPiLKnFIY4k/QpS45zF8W8pG9Wys/e1wM3kd0/BIaEKjLKSuel?= =?iso-8859-1?Q?OitzdxenvBMIu4pXuWOU5A256EEMzXaW1CMVvEk5JLRJg6n9AVIuXbJQ9r?= =?iso-8859-1?Q?5Jz43K5mqfohGMbhVaRyEr8D3p9syOc4/OoXW1YbI4dhdBRt5ieIkFhklJ?= =?iso-8859-1?Q?1U0OmMRPP9MT/aQmaL/PD+TeF29IBdbGbxLgmeMEzzvYCl486IYZ4D7Il1?= =?iso-8859-1?Q?WaSMZDwXfLSN4jpuKnhlRp6apFLTbhvWH7c3qzNVy0bgWwglOq5JFVjOxw?= =?iso-8859-1?Q?fig1KIwJBqLhgF9IWGtH8oJVpR4w7vNl1t6x8LommFmdXH5rKoU31ElLyo?= =?iso-8859-1?Q?CS9PXgD2ERYFi+89j8hFKmax4QdE0ocsx3qUW0wEcfL/LTzjcXtgf9yhTq?= =?iso-8859-1?Q?8LkHHe1RX9423Zb19r9Op+DACedc65nJF0MVcp2JeGqPGpgwHimE3EioPQ?= =?iso-8859-1?Q?P0RVCHvteeCmFjTXZDmkqsxiCOInQnvHZp0bt7z9lkrpbURTh84NV87CgQ?= =?iso-8859-1?Q?uIuGlkXfZf4l84brM1GFbL5xKcgLkD3ZTQg+waqQMts6208+gaJMiFfvJZ?= =?iso-8859-1?Q?YRmPPF6k48aaSItrc1e3yQIcH98HmS6oSnwHTqz5U4O6/3GBa+QcWk1KKy?= =?iso-8859-1?Q?103mhzzqrPwP0TVNFiZeCvQXWa/t3Q5ZG3sGad2LueeD3EIlwqqLz3aH/r?= =?iso-8859-1?Q?oUGpHkwvRA81n1FTKS/vEW51u2r8+W5kttjIQFYBWiKu04HMKQ2YbXhRch?= =?iso-8859-1?Q?29PnoF0pe4MVb05trBmbLtnqZu/OjBzTEdIXv38/dni3kIWSKy08GXdLXG?= =?iso-8859-1?Q?exKa9OdoUB8SvnBzim7GCuui5E+QcU4hIeovfKmnuacJKq5/iMCzYYgn6N?= =?iso-8859-1?Q?vkpHoe9JaLOoM3VDpBy8W9rr+OfSMKb9+fdZLmbude+KIr4=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR00MB07605CD725FD313DCE5BD78AF6FA9BY5PR00MB0760namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR00MB0760.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 121d25c6-376f-4c5f-04bc-08d95e56ee5e
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Aug 2021 12:36:10.8117 (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: s8Uc6AiTZDyaqMoe+OIeafv+bEbrkvhLRBSk+496I/gJ97dPH1JW+jjLgbm8dN5UsgUUnHPG05aQAkNiOaKGEA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR00MB0632
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/4T-oku8YuxfcNYtXfNxoE-ZTnLQ>
Subject: [scim] BoF Review and workshopping the Charter based on SCIM IG call, Aug 4
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 13 Aug 2021 12:36:25 -0000

--_000_BY5PR00MB07605CD725FD313DCE5BD78AF6FA9BY5PR00MB0760namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Apologies for the lateness of this summary!    This note talks through our =
discussion last week on our BoF and on next steps, but the real meat here i=
s the decision making that necessarily needs to move to be email-focused.  =
 Please give us your reactions to the topics below.    Additionally,  our s=
ummary of the meeeting, links to the meeting, and thoughts and goals moving=
 forward are here:  meetings/2021-08-04.md at main =B7 SCIM-Interest-Group/=
meetings (github.com)<https://nam06.safelinks.protection.outlook.com/?url=
=3Dhttps%3A%2F%2Fgithub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%=
2F2021%2F2021-08-04.md&data=3D04%7C01%7CPamela.Dingle%40microsoft.com%7Cb33=
efe0d2d2c4e43269408d958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C=
637638586957227083%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu=
MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D%2BRAJAIV54EP10dGsRdFbVNB=
V%2BvKqOC8HrML7n%2BZFP94%3D&reserved=3D0>. Video of the meeting is availabl=
e on Youtube: https://youtu.be/msGCsG752PA<https://nam06.safelinks.protecti=
on.outlook.com/?url=3Dhttps%3A%2F%2Fyoutu.be%2FmsGCsG752PA&data=3D04%7C01%7=
CPamela.Dingle%40microsoft.com%7Cb33efe0d2d2c4e43269408d958ea8f33%7C72f988b=
f86f141af91ab2d7cd011db47%7C1%7C0%7C637638586957237046%7CUnknown%7CTWFpbGZs=
b3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C10=
00&sdata=3DWyF9Kn51LgCxrAOO5oW2MznY4SsoY57OoZ4axafOeIg%3D&reserved=3D0>



Three issues need surfacing to the wider community, based on commentary in =
the BoF:

Synchronization not a Charter Focus

While we have spoken a lot in our interest group meetings about pagination,=
 comments from Morteza around synchronization sparked a conversation around=
 the relationship between pagination and synchronization -- is it that pagi=
nation is so critical because large data set fetches are the only way to do=
 synchronization?   The consensus from the group in the meeting was that ye=
s, there is a relationship here, and while we definitely still think pagina=
tion is a critical topic, understanding the nature of our syncronization us=
e cases could shed light on why large data set handling is so critical for =
many.

Fixed vs. Discoverable Schema

Discussion of Leif's comments in the BoF about lack of flexibility in curre=
nt schema efforts resulted  the group suggested that we should look at what=
 could be done to better support discoverable schema.  Can we make the disc=
overy mechanism already in the spec more dynamic or more able to be part of=
 a schema negotiation?

Discussion on External ID and Privileged Access

We didn't get a chance to discuss, but are looking for thoughts and discuss=
ion from the community.

Moving towards IETF Conformant Comms and Processes

Nancy Cam Winget (one of our BoF chairs) has been advising us on next steps=
 and the discussion began on process.  The group took a shot at running som=
e consensus calls today in the meeting based on the above topics, you can s=
ee them below and we want your feedback, but going  chairs. Additionally Na=
ncy was very clear that the critical consensus mechanism needs to be the ma=
iling list - so we will work to make sure those motions are properly follow=
ed.

Please give us your thoughts & reactions to these two statements and their =
impact on the proposed charter:


Consensus call (9/11 within the call):  We will explore synchronization pat=
terns and deliver a document describing what implementers are doing, with o=
ne focus being how large data sets are involved as an early deliverable



Consensus call (7/11 within the call) for "investigating discoverable schem=
a as part of our schema milestone" deliverable would be a document containi=
ng recommendations delivered to the WG

Cheers,

Pam


--_000_BY5PR00MB07605CD725FD313DCE5BD78AF6FA9BY5PR00MB0760namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">Hi all,&nbsp;</span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">Apologies for the latenes=
s of this summary!&nbsp; &nbsp; This note talks through our discussion last=
 week on our BoF and on next steps, but the real
 meat here is the decision making that necessarily needs to move to be emai=
l-focused.&nbsp; &nbsp;Please give us your reactions to the topics below.&n=
bsp; &nbsp; Additionally,&nbsp;&nbsp;<span style=3D"color: black; font-size=
: 12pt;">our summary of the meeeting, links to the meeting, and
 thoughts and goals moving forward are here:&nbsp;&nbsp;</span><a href=3D"h=
ttps://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.c=
om%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%2F2021%2F2021-08-04.md&am=
p;data=3D04%7C01%7CPamela.Dingle%40microsoft.com%7Cb33efe0d2d2c4e43269408d9=
58ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637638586957227083%7C=
Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL=
CJXVCI6Mn0%3D%7C1000&amp;sdata=3D%2BRAJAIV54EP10dGsRdFbVNBV%2BvKqOC8HrML7n%=
2BZFP94%3D&amp;reserved=3D0" target=3D"_blank" rel=3D"noopener noreferrer" =
data-auth=3D"Verified" shash=3D"SMMbkK0maWGL2tuykq/u6D3A7oIrhQpzJB3xDcfEPfF=
Zxppk4XytAroc2kFmWNY30MA+GhkbM6fzUWZ/uAaUQK/jt64zOzBrEzPZELjiuScm2cNApw/1oq=
LfqgOYVRqnfBQYlMhZxowQ90OF0IzRt6y1SW9soPNZTJFFW3k7A8M=3D" title=3D"Original=
 URL: https://github.com/SCIM-Interest-Group/meetings/blob/main/2021/2021-0=
8-04.md. Click or tap if you trust this link." data-linkindex=3D"0" style=
=3D"font-size: 12pt;">meetings/2021-08-04.md
 at main =B7 SCIM-Interest-Group/meetings (github.com)</a><span style=3D"co=
lor: black; font-size: 12pt;">.&nbsp;</span><span style=3D"color: black; fo=
nt-size: 12pt;">Video of the meeting is available on Youtube:&nbsp;</span><=
a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F=
%2Fyoutu.be%2FmsGCsG752PA&amp;data=3D04%7C01%7CPamela.Dingle%40microsoft.co=
m%7Cb33efe0d2d2c4e43269408d958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1=
%7C0%7C637638586957237046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI=
joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DWyF9Kn51LgCxrA=
OO5oW2MznY4SsoY57OoZ4axafOeIg%3D&amp;reserved=3D0" target=3D"_blank" rel=3D=
"noopener noreferrer" data-auth=3D"Verified" shash=3D"y6y/+33WPW4umN8yow0Ew=
o3S1ee3OusagYUhrgBCtl+WciyTUq2lXMAYIL1T3NtvqjmVXNIl/QrBfpNnDmFk8wYwtwCjKsXl=
pcNOMUif0V/kOVliMqlHuSsnuDVctd1EO9BjaGWpP10ojxkf9ByKGKzaKKqqYIkrQit+hSzlEpU=
=3D" title=3D"Original URL: https://youtu.be/msGCsG752PA. Click or tap if y=
ou trust this link." data-linkindex=3D"1" style=3D"font-size: 12pt;">https:=
//youtu.be/msGCsG752PA</a></span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black"></p>
<p style=3D"color:rgb(32, 31, 30);font-size:11pt;margin:0px">&nbsp;</p>
</span>
<p></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">Three issues need surfaci=
ng to the wider community, based on commentary in the BoF:</span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Synchronization not a =
Charter Focus</span></b><span style=3D"margin:0px;font-size:12pt;color:blac=
k"></span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">While we have spoken a lo=
t in our interest group meetings about pagination, comments from Morteza ar=
ound synchronization sparked a conversation
 around the relationship between pagination and synchronization -- is it th=
at pagination is so critical because large data set fetches are the only wa=
y to do synchronization?&nbsp; &nbsp;The consensus from the group in the me=
eting was that yes, there is a relationship
 here, and while we definitely still think pagination is a critical topic, =
understanding the nature of our syncronization use cases could shed light o=
n why large data set handling is so critical for many.</span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Fixed vs. Discoverable=
 Schema</span></b><span style=3D"margin:0px;font-size:12pt;color:black"></s=
pan></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">Discussion of Leif's comm=
ents in the BoF about lack of flexibility in current schema efforts resulte=
d&nbsp; the group suggested that we should
 look at what could be done to better support discoverable schema.&nbsp; Ca=
n we make the discovery mechanism already in the spec more dynamic or more =
able to be part of a schema negotiation?</span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Discussion on External=
 ID and Privileged Access</span></b><span style=3D"margin:0px;font-size:12p=
t;color:black"></span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">We didn't get a chance to=
 discuss, but are looking for thoughts and discussion from the community.&n=
bsp;&nbsp;</span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Moving towards IETF Co=
nformant Comms and Processes</span></b><span style=3D"margin:0px;font-size:=
12pt;color:black"></span></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black"><span data-markjs=3D"true=
" class=3D"mark93ggdq4rb" data-ogac=3D"" data-ogab=3D"" data-ogsc=3D"" data=
-ogsb=3D"" style=3D"margin:0px">Nancy</span><span>&nbsp;</span><span data-m=
arkjs=3D"true" class=3D"markn0rq63e6z" data-ogac=3D"" data-ogab=3D"" data-o=
gsc=3D"" data-ogsb=3D"" style=3D"margin:0px">Cam</span><span>&nbsp;</span><=
span data-markjs=3D"true" class=3D"mark2yn8vnlym" data-ogac=3D"" data-ogab=
=3D"" data-ogsc=3D"" data-ogsb=3D"" style=3D"margin:0px">Winget</span><span=
>&nbsp;</span>(one
 of our BoF chairs) has been advising us on next steps and the discussion b=
egan on process.&nbsp; The group took a shot at running some consensus call=
s today in the meeting based on the above topics, you can see them below an=
d we want your feedback, but going&nbsp; chairs.
 Additionally<span>&nbsp;</span><span data-markjs=3D"true" class=3D"mark93g=
gdq4rb" data-ogac=3D"" data-ogab=3D"" data-ogsc=3D"" data-ogsb=3D"" style=
=3D"margin:0px">Nancy</span><span>&nbsp;</span>was very clear that the crit=
ical consensus mechanism needs to be the mailing list - so
 we will work to make sure those motions are properly followed.&nbsp;</span=
></p>
</div>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">Please give us your thoug=
hts &amp; reactions to these two statements and their impact on the propose=
d charter:</span></p>
</div>
<div style=3D"margin:0px;font-size:15px;font-family:&quot;Segoe UI&quot;, &=
quot;Segoe UI Web (West European)&quot;, &quot;Segoe UI&quot;, -apple-syste=
m, BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, sans-serif;color=
:rgb(32, 31, 30);background-color:rgb(255, 255, 255)">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><br>
</p>
</div>
<blockquote style=3D"color:rgb(32, 31, 30);font-family:&quot;Segoe UI&quot;=
, &quot;Segoe UI Web (West European)&quot;, &quot;Segoe UI&quot;, -apple-sy=
stem, BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, sans-serif;fo=
nt-size:15px;background-color:rgb(255, 255, 255)">
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Consensus call (9/11 w=
ithin the call): &nbsp;We will explore synchronization patterns and deliver=
 a document describing what implementers
 are doing, with one focus being how large data sets are involved as an ear=
ly deliverable</span></b><span style=3D"margin:0px;font-size:12pt;color:bla=
ck"></span></p>
</div>
</blockquote>
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><spa=
n style=3D"margin:0px;font-size:12pt;color:black">&nbsp;</span></p>
</div>
<blockquote style=3D"color:rgb(32, 31, 30);font-family:&quot;Segoe UI&quot;=
, &quot;Segoe UI Web (West European)&quot;, &quot;Segoe UI&quot;, -apple-sy=
stem, BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, sans-serif;fo=
nt-size:15px;background-color:rgb(255, 255, 255)">
<div style=3D"margin:0px">
<p style=3D"font-size:11pt;font-family:Calibri, sans-serif;margin:0px"><b><=
span style=3D"margin:0px;font-size:12pt;color:black">Consensus call (7/11 w=
ithin the call) for &quot;investigating discoverable schema as part of our =
schema milestone&quot; deliverable would be a
 document containing recommendations delivered to the WG</span></b></p>
</div>
</blockquote>
Cheers,</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Pam</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
</body>
</html>

--_000_BY5PR00MB07605CD725FD313DCE5BD78AF6FA9BY5PR00MB0760namp_--


From nobody Fri Aug 13 12:52:32 2021
Return-Path: <phil.hunt@independentid.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 A193C3A2453 for <scim@ietfa.amsl.com>; Fri, 13 Aug 2021 12:52:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.297
X-Spam-Level: 
X-Spam-Status: No, score=-0.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, PDS_SHORTFWD_URISHRT_QP=1.499, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 Ye1s15vxwQux for <scim@ietfa.amsl.com>; Fri, 13 Aug 2021 12:52:24 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 240833A2451 for <scim@ietf.org>; Fri, 13 Aug 2021 12:52:23 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id a20so13466785plm.0 for <scim@ietf.org>; Fri, 13 Aug 2021 12:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=5JpFn+0n/MtICDpsmtOCov1GTn6TybNKXx1uI59dC0w=; b=AkJzoOjcrDolFCx4Vl0MNjj4rRfPKzOIOfktPV1Tzjn6cQ2TkgSB2UVPJhmMlBpB+I VVq0tp4dyMJwMTxWlt5eoQD0qyiYbkPK1VVy23BJBhufh+xb9gY5FpPqOS2xRwIe/L3R E2YNTdh5Vo++mqAeLv5boMKscffzZPZF5tTdJxHX+22h2AE1XZO3NouzoPchF5Qsikwp n00ERF8qN2Vm9yv26Fn1KTC1IqgZpdynIInWdRGV4Z04M5IzpDpz9gFVqRyYtm9aU+2l XPdQd2RPd1r35ScuLh0RYbwFmuidSbjo5u7+pVix1PhYigip5bSbcDeBaJRdIsVjz0sI 8TGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=5JpFn+0n/MtICDpsmtOCov1GTn6TybNKXx1uI59dC0w=; b=nBR35FmsRYH3fmL3mVy0NR8ttURK0WRs6QS1mwFg2gWVTRjiejKnKCIVU8Zw6oQmLP LfrizWALCeu2ehQDlaKTcXXWLr7tELqbhkchEjWH4yfqYM94WYhY9ObwcbuOvoga4lc/ WkdmcR/3XW9oblyD2d5ZHSHYPBsEBnxbxjNIva1nzXerWFhRjGpF16NN8UTgC7OY3iWw UpYMmKcDSbOD6C0g+rHXiy2H5F8fUixXLknZMFwQO0Uf7f2VMoFVUTdN9fC8ABai9exf rk883bQjv0/cD0kPUVjctIQ0kxwXje9aSaWBqoXlaJCQjf9dcFfZoGX7rIVvc/xfXblj BYfA==
X-Gm-Message-State: AOAM532KhHdzgyomM2aLVRSOEHDNNVzvHrpn0B5zKtsD9axCZ/p4p7Mp v5Y9OgAVtg/n7l62HrOvp/sWYgAUEZnRNX6z
X-Google-Smtp-Source: ABdhPJzD3KggNIwCcg/DccsA4LgSMS5aLIEKXgG7Y+u41QnGi1BRuPAgbaOwzVGxLiqlelYvzGzMlQ==
X-Received: by 2002:a63:5252:: with SMTP id s18mr3834028pgl.94.1628884341607;  Fri, 13 Aug 2021 12:52:21 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9qrfoxxbd3khma6ktm6d.ipv6.telus.net. [2001:569:7a71:1d00:fc75:4749:9dd6:a185]) by smtp.gmail.com with ESMTPSA id n25sm3105419pfa.26.2021.08.13.12.52.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Aug 2021 12:52:20 -0700 (PDT)
From: Phil Hunt <phil.hunt@independentid.com>
Message-Id: <D961D39B-72E0-463A-B7C0-9E366D0EDDD7@independentid.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4D134C8B-4BD4-4C2B-A10A-60FB0EA63375"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Fri, 13 Aug 2021 12:52:19 -0700
In-Reply-To: <BY5PR00MB07605CD725FD313DCE5BD78AF6FA9@BY5PR00MB0760.namprd00.prod.outlook.com>
Cc: "scim@ietf.org" <scim@ietf.org>
To: Pamela Dingle <Pamela.Dingle=40microsoft.com@dmarc.ietf.org>
References: <BY5PR00MB07605CD725FD313DCE5BD78AF6FA9@BY5PR00MB0760.namprd00.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/9CqZEZ764yvu5Ef4rBQRMFJ_tfE>
Subject: Re: [scim] BoF Review and workshopping the Charter based on SCIM IG call, Aug 4
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 13 Aug 2021 19:52:31 -0000

--Apple-Mail=_4D134C8B-4BD4-4C2B-A10A-60FB0EA63375
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Pam,

Thanks for the notes.  Apologies for not making the last meeting.


Paging and Sync Comments:
In my conversations with Matt Peterson we both have the feeling that the =
request for =E2=80=9Cstateful=E2=80=9D paging of results has to do with =
clients wanting to do synchronization. The technical need is driven by =
memory limitations in clients.  Matt, let me know if I am speaking out =
of turn, but this form of =E2=80=9Cpaging=E2=80=9D for synchronization =
and reconciliation is a =E2=80=9Cpoor-mans=E2=80=9D approach.

I would like to ask if there are other use-cases or need people have for =
stateful paging other than co-ordination and synchronization. If so, =
stateful paging may be worth pursuing given appropriate caveats.

Given this, Synchronization/Co-ordination needs to be explored at least =
in case of requirements as a charter item.  In SCIM environments there =
are many cross-domain scenarios where items are not being replicated. =
However entity life-cycles need to be co-ordinated.  I would like to see =
an approach that works on =E2=80=9Cchanges=E2=80=9D only rather than =
pulling full data sets.  This is an information minimization approach =
and minimizes data transfer.   There are many possible technolgoies we =
could explore:
* Security Event streams (publish/subscribe or event bus).  A stream can =
be explicit or contain simple =E2=80=9Cthis resource has changed=E2=80=9D.=

* Usage of pre-conditions to detect resource changes (date and etag)
* Change date query to detect changed resources (kind of an evolution of =
ldap changelog)
* Reversal of roles.  Service provider acts as client to send changes =
back
* Others TBD

Schemas:
Regarding Leif=E2=80=99s comments, I took him to mean he would ike to =
see servers not built on hard coded or otherwise fixed schema (e.g. =
POJOs).  I didn=E2=80=99t take him to mean that there was protocol work =
to be done here.   My recently published i2scim.io open source =
implementation is an example of this.

=46rom the call I am not sure what was meant by =E2=80=9CDiscoverable =
schema is only useful for optional attributes=E2=80=9D.  In the sense =
that a server should support Users and Groups, there=E2=80=99s nothing =
saying other schemas and resource types can=E2=80=99t be defined and =
optionally registered via IANA.  In that sense, the /ResourceTypes and =
/Schemas endpoints become very meaningful.

I think there is a higher level problem of interring meaning beyond =
Attributes types and characteristics as well as resource type =
definitions that may seem arbitrary. I think this is where the standard =
process is useful.  Any publication process is going to help act as a =
reference for implementers to understand purpose and meaning beyond raw =
data.

Phil Hunt
@independentid
phil.hunt@independentid.com




> On Aug 13, 2021, at 5:36 AM, Pamela Dingle =
<Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org> wrote:
>=20
> Hi all,=20
> Apologies for the lateness of this summary!    This note talks through =
our discussion last week on our BoF and on next steps, but the real meat =
here is the decision making that necessarily needs to move to be =
email-focused.   Please give us your reactions to the topics below.    =
Additionally,  our summary of the meeeting, links to the meeting, and =
thoughts and goals moving forward are here:  meetings/2021-08-04.md at =
main =C2=B7 SCIM-Interest-Group/meetings (github.com) =
<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithu=
b.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%2F2021%2F2021-08-04.m=
d&data=3D04%7C01%7CPamela.Dingle%40microsoft.com%7Cb33efe0d2d2c4e43269408d=
958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637638586957227083%=
7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haW=
wiLCJXVCI6Mn0%3D%7C1000&sdata=3D%2BRAJAIV54EP10dGsRdFbVNBV%2BvKqOC8HrML7n%=
2BZFP94%3D&reserved=3D0>. Video of the meeting is available on Youtube: =
https://youtu.be/msGCsG752PA =
<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fyoutu=
.be%2FmsGCsG752PA&data=3D04%7C01%7CPamela.Dingle%40microsoft.com%7Cb33efe0=
d2d2c4e43269408d958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637=
638586957237046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz=
IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DWyF9Kn51LgCxrAOO5oW2MznY4S=
soY57OoZ4axafOeIg%3D&reserved=3D0>
> =20
> Three issues need surfacing to the wider community, based on =
commentary in the BoF:
> Synchronization not a Charter Focus
> While we have spoken a lot in our interest group meetings about =
pagination, comments from Morteza around synchronization sparked a =
conversation around the relationship between pagination and =
synchronization -- is it that pagination is so critical because large =
data set fetches are the only way to do synchronization?   The consensus =
from the group in the meeting was that yes, there is a relationship =
here, and while we definitely still think pagination is a critical =
topic, understanding the nature of our syncronization use cases could =
shed light on why large data set handling is so critical for many.
> Fixed vs. Discoverable Schema
> Discussion of Leif's comments in the BoF about lack of flexibility in =
current schema efforts resulted  the group suggested that we should look =
at what could be done to better support discoverable schema.  Can we =
make the discovery mechanism already in the spec more dynamic or more =
able to be part of a schema negotiation?
> Discussion on External ID and Privileged Access
> We didn't get a chance to discuss, but are looking for thoughts and =
discussion from the community. =20
> Moving towards IETF Conformant Comms and Processes
> Nancy Cam Winget (one of our BoF chairs) has been advising us on next =
steps and the discussion began on process.  The group took a shot at =
running some consensus calls today in the meeting based on the above =
topics, you can see them below and we want your feedback, but going  =
chairs. Additionally Nancy was very clear that the critical consensus =
mechanism needs to be the mailing list - so we will work to make sure =
those motions are properly followed.=20
> Please give us your thoughts & reactions to these two statements and =
their impact on the proposed charter:
>=20
> Consensus call (9/11 within the call):  We will explore =
synchronization patterns and deliver a document describing what =
implementers are doing, with one focus being how large data sets are =
involved as an early deliverable
> =20
> Consensus call (7/11 within the call) for "investigating discoverable =
schema as part of our schema milestone" deliverable would be a document =
containing recommendations delivered to the WG
> Cheers,
>=20
> Pam
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org <mailto:scim@ietf.org>
> https://www.ietf.org/mailman/listinfo/scim =
<https://www.ietf.org/mailman/listinfo/scim>

--Apple-Mail=_4D134C8B-4BD4-4C2B-A10A-60FB0EA63375
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Pam,<div class=3D""><br class=3D""></div><div class=3D"">Thanks=
 for the notes. &nbsp;Apologies for not making the last =
meeting.</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Paging and Sync Comments:</div><div =
class=3D"">In my conversations with Matt Peterson we both have the =
feeling that the request for =E2=80=9Cstateful=E2=80=9D paging of =
results has to do with clients wanting to do synchronization. The =
technical need is driven by memory limitations in clients. &nbsp;Matt, =
let me know if I am speaking out of turn, but this form of =E2=80=9Cpaging=
=E2=80=9D for synchronization and reconciliation is a =E2=80=9Cpoor-mans=E2=
=80=9D approach.</div><div class=3D""><br class=3D""></div><div =
class=3D"">I would like to ask if there are other use-cases or need =
people have for stateful paging other than co-ordination and =
synchronization. If so, stateful paging may be worth pursuing given =
appropriate caveats.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Given this, Synchronization/Co-ordination needs to be =
explored at least in case of requirements as a charter item. &nbsp;In =
SCIM environments there are many cross-domain scenarios where items are =
not being replicated. However entity life-cycles need to be =
co-ordinated. &nbsp;I would like to see an approach that works on =
=E2=80=9Cchanges=E2=80=9D only rather than pulling full data sets. =
&nbsp;This is an information minimization approach and minimizes data =
transfer. &nbsp; There are many possible technolgoies we could =
explore:</div><div class=3D"">* Security Event streams =
(publish/subscribe or event bus). &nbsp;A stream can be explicit or =
contain simple =E2=80=9Cthis resource has changed=E2=80=9D.</div><div =
class=3D"">* Usage of pre-conditions to detect resource changes (date =
and etag)</div><div class=3D"">* Change date query to detect changed =
resources (kind of an evolution of ldap changelog)</div><div class=3D"">* =
Reversal of roles. &nbsp;Service provider acts as client to send changes =
back</div><div class=3D"">* Others TBD</div><div class=3D""><br =
class=3D""></div><div class=3D"">Schemas:</div><div class=3D"">Regarding =
Leif=E2=80=99s comments, I took him to mean he would ike to see servers =
not built on hard coded or otherwise fixed schema (e.g. POJOs). &nbsp;I =
didn=E2=80=99t take him to mean that there was protocol work to be done =
here. &nbsp; My recently published <a href=3D"http://i2scim.io" =
class=3D"">i2scim.io</a> open source implementation is an example of =
this.</div><div class=3D""><br class=3D""></div><div class=3D"">=46rom =
the call I am not sure what was meant by =E2=80=9CDiscoverable schema is =
only useful for optional attributes=E2=80=9D. &nbsp;In the sense that a =
server should support Users and Groups, there=E2=80=99s nothing saying =
other schemas and resource types can=E2=80=99t be defined and optionally =
registered via IANA. &nbsp;In that sense, the /ResourceTypes and =
/Schemas endpoints become very meaningful.</div><div class=3D""><br =
class=3D""></div><div class=3D"">I think there is a higher level problem =
of interring meaning beyond Attributes types and characteristics as well =
as resource type definitions that may seem arbitrary. I think this is =
where the standard process is useful. &nbsp;Any publication process is =
going to help act as a reference for implementers to understand purpose =
and meaning beyond raw data.</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">
<div dir=3D"auto" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0); letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: =
break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D""><div>Phil Hunt</div><div>@independentid</div><div><a =
href=3D"mailto:phil.hunt@independentid.com" =
class=3D"">phil.hunt@independentid.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Aug 13, 2021, at 5:36 AM, Pamela Dingle &lt;<a =
href=3D"mailto:Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org" =
class=3D"">Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Arial, Helvetica, =
sans-serif; font-size: 12pt;" class=3D""><div style=3D"margin: 0px;" =
class=3D""><div style=3D"margin: 0px; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><span style=3D"margin: 0px; font-size: =
12pt;" class=3D"">Hi all,&nbsp;</span></div></div><div style=3D"margin: =
0px;" class=3D""><div style=3D"margin: 0px; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><span style=3D"margin: =
0px; font-size: 12pt;" class=3D"">Apologies for the lateness of this =
summary!&nbsp; &nbsp; This note talks through our discussion last week =
on our BoF and on next steps, but the real meat here is the decision =
making that necessarily needs to move to be email-focused.&nbsp; =
&nbsp;Please give us your reactions to the topics below.&nbsp; &nbsp; =
Additionally,&nbsp;&nbsp;<span style=3D"font-size: 12pt;" class=3D"">our =
summary of the meeeting, links to the meeting, and thoughts and goals =
moving forward are here:&nbsp;&nbsp;</span><a =
href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%=
2Fgithub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%2F2021%2F2021-=
08-04.md&amp;data=3D04%7C01%7CPamela.Dingle%40microsoft.com%7Cb33efe0d2d2c=
4e43269408d958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63763858=
6957227083%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ=
BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D%2BRAJAIV54EP10dGsRdFbVNBV%=
2BvKqOC8HrML7n%2BZFP94%3D&amp;reserved=3D0" target=3D"_blank" =
rel=3D"noopener noreferrer" data-auth=3D"Verified" =
shash=3D"SMMbkK0maWGL2tuykq/u6D3A7oIrhQpzJB3xDcfEPfFZxppk4XytAroc2kFmWNY30=
MA+GhkbM6fzUWZ/uAaUQK/jt64zOzBrEzPZELjiuScm2cNApw/1oqLfqgOYVRqnfBQYlMhZxow=
Q90OF0IzRt6y1SW9soPNZTJFFW3k7A8M=3D" title=3D"Original URL: =
https://github.com/SCIM-Interest-Group/meetings/blob/main/2021/2021-08-04.=
md. Click or tap if you trust this link." data-linkindex=3D"0" =
style=3D"font-size: 12pt;" class=3D"">meetings/2021-08-04.md at main =C2=B7=
 SCIM-Interest-Group/meetings (github.com)</a><span style=3D"font-size: =
12pt;" class=3D"">.&nbsp;</span><span style=3D"font-size: 12pt;" =
class=3D"">Video of the meeting is available on Youtube:&nbsp;</span><a =
href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%=
2Fyoutu.be%2FmsGCsG752PA&amp;data=3D04%7C01%7CPamela.Dingle%40microsoft.co=
m%7Cb33efe0d2d2c4e43269408d958ea8f33%7C72f988bf86f141af91ab2d7cd011db47%7C=
1%7C0%7C637638586957237046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ=
QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DWyF9Kn51LgC=
xrAOO5oW2MznY4SsoY57OoZ4axafOeIg%3D&amp;reserved=3D0" target=3D"_blank" =
rel=3D"noopener noreferrer" data-auth=3D"Verified" =
shash=3D"y6y/+33WPW4umN8yow0Ewo3S1ee3OusagYUhrgBCtl+WciyTUq2lXMAYIL1T3Ntvq=
jmVXNIl/QrBfpNnDmFk8wYwtwCjKsXlpcNOMUif0V/kOVliMqlHuSsnuDVctd1EO9BjaGWpP10=
ojxkf9ByKGKzaKKqqYIkrQit+hSzlEpU=3D" title=3D"Original URL: =
https://youtu.be/msGCsG752PA. Click or tap if you trust this link." =
data-linkindex=3D"1" style=3D"font-size: 12pt;" =
class=3D"">https://youtu.be/msGCsG752PA</a></span></div></div><div =
style=3D"margin: 0px;" class=3D""><p style=3D"margin: 0px; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span style=3D"margin:=
 0px; font-size: 12pt;" class=3D""></span></p><p style=3D"margin: 0px; =
color: rgb(32, 31, 30); font-size: 11pt;" class=3D"">&nbsp;</p><p =
style=3D"margin-top: 0px; margin-bottom: 0px;" class=3D""></p></div><div =
style=3D"margin: 0px;" class=3D""><div style=3D"margin: 0px; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span style=3D"margin:=
 0px; font-size: 12pt;" class=3D"">Three issues need surfacing to the =
wider community, based on commentary in the BoF:</span></div></div><div =
style=3D"margin: 0px;" class=3D""><div style=3D"margin: 0px; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><b class=3D""><span =
style=3D"margin: 0px; font-size: 12pt;" class=3D"">Synchronization not a =
Charter Focus</span></b><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D""></span></div></div><div style=3D"margin: 0px;" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D"">While we have spoken a lot in our interest group meetings =
about pagination, comments from Morteza around synchronization sparked a =
conversation around the relationship between pagination and =
synchronization -- is it that pagination is so critical because large =
data set fetches are the only way to do synchronization?&nbsp; &nbsp;The =
consensus from the group in the meeting was that yes, there is a =
relationship here, and while we definitely still think pagination is a =
critical topic, understanding the nature of our syncronization use cases =
could shed light on why large data set handling is so critical for =
many.</span></div></div><div style=3D"margin: 0px;" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><b class=3D""><span style=3D"margin: 0px; =
font-size: 12pt;" class=3D"">Fixed vs. Discoverable =
Schema</span></b><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D""></span></div></div><div style=3D"margin: 0px;" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D"">Discussion of Leif's comments in the BoF about lack of =
flexibility in current schema efforts resulted&nbsp; the group suggested =
that we should look at what could be done to better support discoverable =
schema.&nbsp; Can we make the discovery mechanism already in the spec =
more dynamic or more able to be part of a schema =
negotiation?</span></div></div><div style=3D"margin: 0px;" class=3D""><div=
 style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><b class=3D""><span style=3D"margin: 0px; =
font-size: 12pt;" class=3D"">Discussion on External ID and Privileged =
Access</span></b><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D""></span></div></div><div style=3D"margin: 0px;" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D"">We didn't get a chance to discuss, but are looking for =
thoughts and discussion from the =
community.&nbsp;&nbsp;</span></div></div><div style=3D"margin: 0px;" =
class=3D""><div style=3D"margin: 0px; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><b class=3D""><span style=3D"margin: =
0px; font-size: 12pt;" class=3D"">Moving towards IETF Conformant Comms =
and Processes</span></b><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D""></span></div></div><div style=3D"margin: 0px;" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D""><span data-markjs=3D"true" class=3D"mark93ggdq4rb" =
data-ogac=3D"" data-ogab=3D"" data-ogsc=3D"" data-ogsb=3D"" =
style=3D"margin: 0px;">Nancy</span><span class=3D"">&nbsp;</span><span =
data-markjs=3D"true" class=3D"markn0rq63e6z" data-ogac=3D"" data-ogab=3D""=
 data-ogsc=3D"" data-ogsb=3D"" style=3D"margin: 0px;">Cam</span><span =
class=3D"">&nbsp;</span><span data-markjs=3D"true" class=3D"mark2yn8vnlym"=
 data-ogac=3D"" data-ogab=3D"" data-ogsc=3D"" data-ogsb=3D"" =
style=3D"margin: 0px;">Winget</span><span class=3D"">&nbsp;</span>(one =
of our BoF chairs) has been advising us on next steps and the discussion =
began on process.&nbsp; The group took a shot at running some consensus =
calls today in the meeting based on the above topics, you can see them =
below and we want your feedback, but going&nbsp; chairs. =
Additionally<span class=3D"">&nbsp;</span><span data-markjs=3D"true" =
class=3D"mark93ggdq4rb" data-ogac=3D"" data-ogab=3D"" data-ogsc=3D"" =
data-ogsb=3D"" style=3D"margin: 0px;">Nancy</span><span =
class=3D"">&nbsp;</span>was very clear that the critical consensus =
mechanism needs to be the mailing list - so we will work to make sure =
those motions are properly followed.&nbsp;</span></div></div><div =
style=3D"margin: 0px;" class=3D""><div style=3D"margin: 0px; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span style=3D"margin:=
 0px; font-size: 12pt;" class=3D"">Please give us your thoughts &amp; =
reactions to these two statements and their impact on the proposed =
charter:</span></div></div><div style=3D"margin: 0px; font-size: 15px; =
font-family: &quot;Segoe UI&quot;, &quot;Segoe UI Web (West =
European)&quot;, &quot;Segoe UI&quot;, -apple-system, =
BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, sans-serif; =
color: rgb(32, 31, 30); background-color: rgb(255, 255, 255);" =
class=3D""><div style=3D"margin: 0px; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><br class=3D""></div></div><blockquote =
style=3D"color: rgb(32, 31, 30); font-family: &quot;Segoe UI&quot;, =
&quot;Segoe UI Web (West European)&quot;, &quot;Segoe UI&quot;, =
-apple-system, BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, =
sans-serif; font-size: 15px; background-color: rgb(255, 255, 255);" =
class=3D""><div style=3D"margin: 0px;" class=3D""><div style=3D"margin: =
0px; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D"">Consensus call (9/11 within the call): &nbsp;We will explore =
synchronization patterns and deliver a document describing what =
implementers are doing, with one focus being how large data sets are =
involved as an early deliverable</span></b><span style=3D"margin: 0px; =
font-size: 12pt;" class=3D""></span></div></div></blockquote><div =
style=3D"margin: 0px;" class=3D""><p style=3D"margin: 0px; font-size: =
11pt; font-family: Calibri, sans-serif;" class=3D""><span style=3D"margin:=
 0px; font-size: 12pt;" class=3D"">&nbsp;</span></p></div><blockquote =
style=3D"color: rgb(32, 31, 30); font-family: &quot;Segoe UI&quot;, =
&quot;Segoe UI Web (West European)&quot;, &quot;Segoe UI&quot;, =
-apple-system, BlinkMacSystemFont, Roboto, &quot;Helvetica Neue&quot;, =
sans-serif; font-size: 15px; background-color: rgb(255, 255, 255);" =
class=3D""><div style=3D"margin: 0px;" class=3D""><div style=3D"margin: =
0px; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"margin: 0px; font-size: 12pt;" =
class=3D"">Consensus call (7/11 within the call) for "investigating =
discoverable schema as part of our schema milestone" deliverable would =
be a document containing recommendations delivered to the =
WG</span></b></div></div></blockquote>Cheers,</div><div =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; font-family: =
Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=3D""><br =
class=3D""></div><div style=3D"font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: =
12pt;" class=3D"">Pam</div><div style=3D"font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; font-family: Calibri, Arial, Helvetica, =
sans-serif; font-size: 12pt;" class=3D""><br class=3D""></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">scim mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:scim@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">scim@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/scim" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/scim</a></div></blockquot=
e></div><br class=3D""></div></body></html>=

--Apple-Mail=_4D134C8B-4BD4-4C2B-A10A-60FB0EA63375--


From nobody Mon Aug 16 11:07:44 2021
Return-Path: <Matt.Peterson@oneidentity.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 7C81A3A0AE7 for <scim@ietfa.amsl.com>; Mon, 16 Aug 2021 11:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oneidentity.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 yv_8j3H7vgrR for <scim@ietfa.amsl.com>; Mon, 16 Aug 2021 11:07:36 -0700 (PDT)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2100.outbound.protection.outlook.com [40.107.236.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B091B3A0ADB for <scim@ietf.org>; Mon, 16 Aug 2021 11:07:35 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eKV6rv7iR7pcLghauq+TINyJ4dpMD0nrGbbW6G310gMjV8ccUiKJ90cIJiSM42hgkhnuO0R0ap8/am/ggYOTwLPsSN8b3cuUdDqW8aKxp231FePdCriUsNvMlbfbZDma+y8WKMNxEr4RU2gtGAZEUeOIinWGK8fO+BXvsDm5ePTIEMDoKfcGDqgmhEcawrTqr4h7We0sPp+V3/ldeIDUTEAChry4WJ6JaxtArSL84PXd8daXT9gh9KD5piNW02VqtPUwvRNhoZ2Ei17T6JeT5w866K1f+0FZTgS8X5I1KQBSFRWDessLHDN6i0GyfUsmSJVvkZQVoPbZWG0taq3eUg==
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=w9kxxmHb4HgHykCK8fMNDs5uYkJT8HdGvIyhld314gk=; b=hovi/3tAse6L0XdLJsJqq+tmjSxRQH1E2qJxSXOiQP3CvDcs0efP7k0wIxqxU7yn6RdC0vtTNbs+FAVVJ+ibDJBLVIlZpBYJQm/ZrO0OProugu4wC39zfZC+BYoBunqtO2w/DRj2PDBZJ6dliBbiCqETzGVd41yi9jia5WWGGNFUmVnTPGtai+3MhaIjIUhTvGL4S62BFMdEvHAKzjVeVQ0fY+VT+TrTOgyATaIyVAq9Od2v+WBOJq74FdPnkIb0FSon1o+VlP9E/aPa96QElpN7hVfq2yAG6vRfWMcwza15auS6qVPkMY3qlDErQSRacv6s72XrZrnyEkoM+tBHOA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oneidentity.com; dmarc=pass action=none header.from=oneidentity.com; dkim=pass header.d=oneidentity.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oneidentity.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=w9kxxmHb4HgHykCK8fMNDs5uYkJT8HdGvIyhld314gk=; b=Mov4973vsuF2dUCh9DUAOaRL2qo4XtW2d3W5GfRKQq20cBJv+BVmH8zOqbNtc4deccY64vVvk0ZwqoR4JiN3wSZdZyox/LIw8qKGQMhGpXYtlX6qiTn5CKBi5wyZcItatMP2MDwHayrhX0N0j7F0cvohGdHc87KBwjLk01qO04ASqEel8w+T5ieMLC/ERimsezVOt+gQ3UpGWa5sTe4XNBLfh0eKYWkBYCnkqXs8dHL5N2n5h/L5yTCR88Ruhdg1z7MRkkT4k6KGlhKk9ayRMk6gqPLk/VN2PurrvOekjFla230Qc1x4+yp9tZ1Add7ISuVsIpT8d4wXfkiakhu5kQ==
Received: from MWHPR19MB0957.namprd19.prod.outlook.com (2603:10b6:300:a4::16) by MW3PR19MB4300.namprd19.prod.outlook.com (2603:10b6:303:49::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.16; Mon, 16 Aug 2021 18:07:26 +0000
Received: from MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783]) by MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783%4]) with mapi id 15.20.4415.023; Mon, 16 Aug 2021 18:07:26 +0000
From: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
To: Phil Hunt <phil.hunt@independentid.com>
CC: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: [scim] BoF Review and workshopping the Charter based on SCIM IG call, Aug 4
Thread-Index: AQHXkD59zrEiCh3RDEuUBvNOedb2qqtx2PWAgARyZeA=
Date: Mon, 16 Aug 2021 18:07:26 +0000
Message-ID: <MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9@MWHPR19MB0957.namprd19.prod.outlook.com>
References: <BY5PR00MB07605CD725FD313DCE5BD78AF6FA9@BY5PR00MB0760.namprd00.prod.outlook.com> <D961D39B-72E0-463A-B7C0-9E366D0EDDD7@independentid.com>
In-Reply-To: <D961D39B-72E0-463A-B7C0-9E366D0EDDD7@independentid.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: independentid.com; dkim=none (message not signed) header.d=none;independentid.com; dmarc=none action=none header.from=oneidentity.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 69323e5b-9218-4f6e-6192-08d960e0b44d
x-ms-traffictypediagnostic: MW3PR19MB4300:
x-microsoft-antispam-prvs: <MW3PR19MB43008CEA96DF0CC34D797CEBE1FD9@MW3PR19MB4300.namprd19.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uC+fE5J8xP3R2ZBsZBiP8M2xB4Vqco55pfyOJSxL7j0/SspgGdxRx3JYt5LxTMPSHgWEBlCmzKSiEY8WfQzCbRFO8f7OCOooZLVkld1YvyZ0biGP2ba4qy4dxiJFTFw/pDsuStxtU93p/KJ4Es3zytrSnqSXxXa2JR9pEC6xCPZCj2EtUgYNY9ngPA7/yn/J4N59GnnUyFIPZWtrV82UEoJdV5sesc/p2PHnopHDO0OF2BmGlHGp1GyCQ6LA8NEFguErqxPw6y8lrvT4QoJLxmRC3nWgyRyVBmAvUzSOwNp0f/wHYk6B6FVsvyI4+JLhPuyhg6+0H0QjEsDcLztnngwk1+bSaKQq0sg8vjbzGRdwhSUj1OQlQNZtEIskWoom02oA0GYMCAfSLy087BLSHNmZ8T5SIDhQwtc8yiVUmgglhUR+R9t9HCeRGJKK/kWAS/E/ExrWotmMmOCjT4pNs/qxEXlwJ+gSHeB79iKZjwfGCdQ8kiTwDTIp+7aC+cqz09R5q7+pK0Vxce5+aphZc3Sm680KWEgtW7FPyalk93RPgEnkdhshK4iggacG1nBK1GEsMCHuzoZpTUSc1AjKrfF0M2XwWH/eC/9BDMEeBCCCM/iU3/gvxwNb0KjqxVe52G35r7ddBIvokJgI2auy6zq9O2jbJP2iNo7dyqFOQe07IimOGl4eOaKCy8dOXvHA2Cn1map6bgsN9JAC+4/JigUczTRmWmalUI3xpnkUmmumtrYXYZG0QVOoWj/ui/DRu7RNvRT5O1xIyFFZCsri0Av+nm+OGqQUVw/+eB5VqvA=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MWHPR19MB0957.namprd19.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(39860400002)(136003)(396003)(346002)(376002)(9686003)(52536014)(5660300002)(83380400001)(966005)(316002)(478600001)(166002)(86362001)(33656002)(122000001)(71200400001)(6916009)(66446008)(76116006)(66476007)(66556008)(66946007)(38100700002)(6506007)(7696005)(8936002)(64756008)(38070700005)(55016002)(2906002)(53546011)(4326008)(8676002)(186003); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?hjTmK6wIUzv4bVcH4WT3lsger2i3VftOcPIb4TfeJ9AQBs1Y1Kg4cnf4QKx+?= =?us-ascii?Q?ET+3LWVC0mriACMyWlmtGRwWAK7N5cz7vV8SaGqHTN//J6gNkiEqGk7DJ3NN?= =?us-ascii?Q?wn5vNKJ+vRPLGqDgz9/WgkPNxcFm+bR0H693lGDYvOwWFYcFTy9oxdqfaZn/?= =?us-ascii?Q?uszz+fOWziGsfxOLbAYTYHEZmEMO4XrY4x+2qD6XS9+hoQmSUnqcX6wgVn94?= =?us-ascii?Q?NdxWvqu7M8cFK9bENuU+msVV3Knv1nOIQZcBhpcTszrQ2ze2IKmO98XYrUHS?= =?us-ascii?Q?WhYn8uGr1DH/WCvveqyNjvQKc8ko9oi4BoOeLfyYkN4sc65bi8aq1wZevlaG?= =?us-ascii?Q?qKY69HMzv7xvcvkEw4NMAxtkjf91Lw3FuIDtrKczVwmIJC4EWFXDjpNq4OjX?= =?us-ascii?Q?MQxqA20ktM8eZI9xf3+9qLYE2qVjeO+ST/791L0TopR7HW6SUf+yFfxjem5K?= =?us-ascii?Q?AjYMfrmu3AKFCl3jdY6GDotrUajD5+Yxbuwb3Nmq0ts8r3zfVkuRPqhDxeXa?= =?us-ascii?Q?25FQ07CUVcBnTn9bzuHn/TqHLExf2cr3FuNmBIi641TsISXs0hKKlpCtwncn?= =?us-ascii?Q?ukXUwNLIrb9p/CJo9ziNWzUiHD8wX1kHWv/A8uhhD2JW8bThlub4SmLyeF1j?= =?us-ascii?Q?hfjE9B9b2hDnR3vcNRhjFTJHxrWCZw+EBAO2zyXa370ADwOLuMoDr2KYXdlC?= =?us-ascii?Q?AOCO0SMTV1/AnqwwujEEFq+/o6Jir8p/2VSMrz1W+YQ+woUmBIwa9DtcmUdy?= =?us-ascii?Q?zt/oSWMfZrdA+UJW1A8qW0rKfWvPp92ZqWwhdySq1Q95Zyu5VKBOMzKr15pg?= =?us-ascii?Q?CQxspWeJtV+AtSQPkfOr3JEV4XjgxUMBqEUCNeCL27ZALJKctJQwApN9HBY3?= =?us-ascii?Q?YRoxivXgapMHryYIJs3vejfwBx+SmaybtmHzA9xxT8YzxtQqUWsFv/3Jwwah?= =?us-ascii?Q?jzixaSjiHiMdYzt0mAVImPggLfeekTBXBAA1NQ4WDGA494itxiPI5WphsSB8?= =?us-ascii?Q?C+cx9LgHBcq/qml8bEYPj9yGII0loTWZqALcdvZMBnL8Gx2K8Ufe7uuqukOM?= =?us-ascii?Q?G2cI2BGNwIfkk42T+CipB/fTctByVPr8TNhfsBqIS6GN/LZtv2iYkkv13Dej?= =?us-ascii?Q?hNanz7ppRH3pngl6OFK7DRLIk8L1UKEL+e2IWFUlXgB10ImRRdI0uVTHhfuq?= =?us-ascii?Q?5KCB3TryVNdD7+qHUFxl9rOdfxBZYBYrDD0c6M2BT/EZcVBnESAsUr4egtPS?= =?us-ascii?Q?UHPkQb039jeM9kya29A81UfJMpJyXmh1h1Zy7vOBG/o1ZsXlw3kpgdEbBSYJ?= =?us-ascii?Q?iZJHQeicIcgyGxRrjqXRj+UbBwK5RTZHePha42ty5au+pFulSwz/PmbEDouc?= =?us-ascii?Q?Jq9AxSBm1fw4l1zlaucS5whLraop?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9MWHPR19MB0957namp_"
MIME-Version: 1.0
X-OriginatorOrg: oneidentity.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR19MB0957.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 69323e5b-9218-4f6e-6192-08d960e0b44d
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Aug 2021 18:07:26.2717 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 91c369b5-1c9e-439c-989c-1867ec606603
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Knx7FH9QpPFxRNleS9JzEfAYLnnIcGhk2SHk3pQLRTTZcPTl8W1Dp4De6aBsfW5vKUpWjFvjXLH/RCfS1rYiKg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR19MB4300
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/WcKJGM-DmmaasmVdFu3nJ7fmc7A>
Subject: Re: [scim] BoF Review and workshopping the Charter based on SCIM IG call, Aug 4
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 16 Aug 2021 18:07:43 -0000

--_000_MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9MWHPR19MB0957namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Phil,

I agree.  I think that "client-side caching" (sync) of users and groups is =
a common use case for pagination because large results are generated not on=
ly the initial load of objects but also when trying to detect deletions (es=
pecially deletion of group memberships).  There must be a better (more effi=
cient way) of handling this use case than polling with expensive queries.

Like you, I'd really like to get people to post their pagination use cases =
so that we can categorize them.  I thought about posting to this mailing li=
st with a follow up call for pagination use cases.

But I also, I agree with what Parul said on the the Aug 4 call (from the me=
eting notes):

Parul: we do need cursor-based pagination, and that is unlikely to go away =
but it doesn't harm to first define the synchronization world and then look=
 at whether pagination needs to be enhanced...

Parul's suggestion on ordering the tasks is a good one.  It might be useful=
 to get a consensus on "synchronization use case" first.  Then dig into pag=
ination so that we're not trying to talk to both at the same time.

On the topic of synchronization, I think there are two common use cases:


  1.  Constructing and enforcing Application authorization models -  An app=
lication (acting as a SCIM client) caches users/groups data from the IdP in=
 order to present "user/group pickers" when presenting screens used to conf=
igure the application  authorization rules (RBAC, Policy, or ACL).  Also, w=
hen the application enforces authorization, user and group data needs to be=
 immediately available so that authorization decisions can be made quickly.
  2.  Identity Management and Governance systems - implement a canonical id=
entity model" where all accounts and groups are represented.  This model is=
 used to build provisioning rules and calculate separation of duty violatio=
ns, attestations, and approvals etc.   Management-time evaluation of the mo=
del needs to be done efficiently without external calls to the SCIM service=
 provider.

Both of the above use cases, are client-cache use cases -- a "one-way" sync=
:  a) download the initial results and, b) keep the results up to date with=
 changes that are being made on the SCIM Service provider.

It think it could help us narrow down the list of suitable approaches if we=
 could agree that "one-way" sync (keeping a client-side cache up to date) i=
s our target.

--
Matt

From: scim <scim-bounces@ietf.org> On Behalf Of Phil Hunt
Sent: Friday, August 13, 2021 1:52 PM
To: Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org>
Cc: scim@ietf.org
Subject: Re: [scim] BoF Review and workshopping the Charter based on SCIM I=
G call, Aug 4

CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.

Pam,

Thanks for the notes.  Apologies for not making the last meeting.


Paging and Sync Comments:
In my conversations with Matt Peterson we both have the feeling that the re=
quest for "stateful" paging of results has to do with clients wanting to do=
 synchronization. The technical need is driven by memory limitations in cli=
ents.  Matt, let me know if I am speaking out of turn, but this form of "pa=
ging" for synchronization and reconciliation is a "poor-mans" approach.

I would like to ask if there are other use-cases or need people have for st=
ateful paging other than co-ordination and synchronization. If so, stateful=
 paging may be worth pursuing given appropriate caveats.

Given this, Synchronization/Co-ordination needs to be explored at least in =
case of requirements as a charter item.  In SCIM environments there are man=
y cross-domain scenarios where items are not being replicated. However enti=
ty life-cycles need to be co-ordinated.  I would like to see an approach th=
at works on "changes" only rather than pulling full data sets.  This is an =
information minimization approach and minimizes data transfer.   There are =
many possible technolgoies we could explore:
* Security Event streams (publish/subscribe or event bus).  A stream can be=
 explicit or contain simple "this resource has changed".
* Usage of pre-conditions to detect resource changes (date and etag)
* Change date query to detect changed resources (kind of an evolution of ld=
ap changelog)
* Reversal of roles.  Service provider acts as client to send changes back
* Others TBD

Schemas:
Regarding Leif's comments, I took him to mean he would ike to see servers n=
ot built on hard coded or otherwise fixed schema (e.g. POJOs).  I didn't ta=
ke him to mean that there was protocol work to be done here.   My recently =
published i2scim.io<https://nam12.safelinks.protection.outlook.com/?url=3Dh=
ttp%3A%2F%2Fi2scim.io%2F&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d3=
5b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C63=
7644811626277847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz=
IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3Dqxy0%2BxCMe4vJ7A3HZ5hmAlEkz=
czsvq52fOBsRfZ7h%2BY%3D&reserved=3D0> open source implementation is an exam=
ple of this.

>From the call I am not sure what was meant by "Discoverable schema is only =
useful for optional attributes".  In the sense that a server should support=
 Users and Groups, there's nothing saying other schemas and resource types =
can't be defined and optionally registered via IANA.  In that sense, the /R=
esourceTypes and /Schemas endpoints become very meaningful.

I think there is a higher level problem of interring meaning beyond Attribu=
tes types and characteristics as well as resource type definitions that may=
 seem arbitrary. I think this is where the standard process is useful.  Any=
 publication process is going to help act as a reference for implementers t=
o understand purpose and meaning beyond raw data.

Phil Hunt
@independentid
phil.hunt@independentid.com<mailto:phil.hunt@independentid.com>




On Aug 13, 2021, at 5:36 AM, Pamela Dingle <Pamela.Dingle=3D40microsoft.com=
@dmarc.ietf.org<mailto:Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org>> wro=
te:

Hi all,
Apologies for the lateness of this summary!    This note talks through our =
discussion last week on our BoF and on next steps, but the real meat here i=
s the decision making that necessarily needs to move to be email-focused.  =
 Please give us your reactions to the topics below.    Additionally,  our s=
ummary of the meeeting, links to the meeting, and thoughts and goals moving=
 forward are here:  meetings/2021-08-04.md at main * SCIM-Interest-Group/me=
etings (github.com)<https://nam12.safelinks.protection.outlook.com/?url=3Dh=
ttps%3A%2F%2Fgithub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%2F20=
21%2F2021-08-04.md&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff4=
a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C63764481=
1626287844%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB=
TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3DNbBTKbHYd8E2X%2BnqvYAfPMUhZzP6pJI=
RNa4q%2Bbck8pA%3D&reserved=3D0>. Video of the meeting is available on Youtu=
be: https://youtu.be/msGCsG752PA<https://nam12.safelinks.protection.outlook=
.com/?url=3Dhttps%3A%2F%2Fyoutu.be%2FmsGCsG752PA&data=3D04%7C01%7Cmatt.pete=
rson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1=
867ec606603%7C0%7C1%7C637644811626297841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC=
4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3Dq5p=
ABg2LL5A5%2FtK%2B5b2RONXNYJvHbvul%2FmIi6NIzwd0%3D&reserved=3D0>

Three issues need surfacing to the wider community, based on commentary in =
the BoF:
Synchronization not a Charter Focus
While we have spoken a lot in our interest group meetings about pagination,=
 comments from Morteza around synchronization sparked a conversation around=
 the relationship between pagination and synchronization -- is it that pagi=
nation is so critical because large data set fetches are the only way to do=
 synchronization?   The consensus from the group in the meeting was that ye=
s, there is a relationship here, and while we definitely still think pagina=
tion is a critical topic, understanding the nature of our syncronization us=
e cases could shed light on why large data set handling is so critical for =
many.
Fixed vs. Discoverable Schema
Discussion of Leif's comments in the BoF about lack of flexibility in curre=
nt schema efforts resulted  the group suggested that we should look at what=
 could be done to better support discoverable schema.  Can we make the disc=
overy mechanism already in the spec more dynamic or more able to be part of=
 a schema negotiation?
Discussion on External ID and Privileged Access
We didn't get a chance to discuss, but are looking for thoughts and discuss=
ion from the community.
Moving towards IETF Conformant Comms and Processes
Nancy Cam Winget (one of our BoF chairs) has been advising us on next steps=
 and the discussion began on process.  The group took a shot at running som=
e consensus calls today in the meeting based on the above topics, you can s=
ee them below and we want your feedback, but going  chairs. Additionally Na=
ncy was very clear that the critical consensus mechanism needs to be the ma=
iling list - so we will work to make sure those motions are properly follow=
ed.
Please give us your thoughts & reactions to these two statements and their =
impact on the proposed charter:

Consensus call (9/11 within the call):  We will explore synchronization pat=
terns and deliver a document describing what implementers are doing, with o=
ne focus being how large data sets are involved as an early deliverable

Consensus call (7/11 within the call) for "investigating discoverable schem=
a as part of our schema milestone" deliverable would be a document containi=
ng recommendations delivered to the WG
Cheers,

Pam

_______________________________________________
scim mailing list
scim@ietf.org<mailto:scim@ietf.org>
https://www.ietf.org/mailman/listinfo/scim<https://nam12.safelinks.protecti=
on.outlook.com/?url=3Dhttps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fsci=
m&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93=
e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C637644811626307835%7CUnkn=
own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV=
CI6Mn0%3D%7C3000&sdata=3DSkaa6SfAZRcFCpVgRW8vQ8DZXTVgrHYXlbB7stowng8%3D&res=
erved=3D0>


--_000_MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9MWHPR19MB0957namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.mark93ggdq4rb
	{mso-style-name:mark93ggdq4rb;}
span.markn0rq63e6z
	{mso-style-name:markn0rq63e6z;}
span.mark2yn8vnlym
	{mso-style-name:mark2yn8vnlym;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:299384330;
	mso-list-type:hybrid;
	mso-list-template-ids:1159365806 661139940 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:22.8pt;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:58.8pt;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:94.8pt;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:130.8pt;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:166.8pt;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:202.8pt;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:238.8pt;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:274.8pt;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:310.8pt;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:838347036;
	mso-list-type:hybrid;
	mso-list-template-ids:1925614726 67698705 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1092701144;
	mso-list-template-ids:-498808848;}
@list l2:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l2:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3
	{mso-list-id:1306930954;
	mso-list-type:hybrid;
	mso-list-template-ids:-1234386548 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l3:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:41.0pt;
	text-indent:-.25in;}
@list l3:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:77.0pt;
	text-indent:-.25in;}
@list l3:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:113.0pt;
	text-indent:-9.0pt;}
@list l3:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:149.0pt;
	text-indent:-.25in;}
@list l3:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:185.0pt;
	text-indent:-.25in;}
@list l3:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:221.0pt;
	text-indent:-9.0pt;}
@list l3:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:257.0pt;
	text-indent:-.25in;}
@list l3:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:293.0pt;
	text-indent:-.25in;}
@list l3:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:329.0pt;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Phil, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I agree.&nbsp; I think that &#8220;client-side cachi=
ng&#8221; (sync) of users and groups is a common use case for pagination be=
cause large results are generated not only the initial load of objects but =
also when trying to detect deletions (especially deletion
 of group memberships).&nbsp; There must be a better (more efficient way) o=
f handling this use case than polling with expensive queries.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Like you, I&#8217;d really like to get people to pos=
t their pagination use cases so that we can categorize them. &nbsp;I though=
t about posting to this mailing list with a follow up call for pagination u=
se cases.&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">But I also, I agree with what Parul said on the the =
Aug 4 call (from the meeting notes):<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in"><i>Parul: we do need curs=
or-based pagination, and that is unlikely to go away but it doesn't harm to=
 first define the synchronization world and then look at whether pagination=
 needs to be enhanced&#8230;<o:p></o:p></i></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Parul&#8217;s suggestion on ordering the tasks is a =
good one.&nbsp; It might be useful to get a consensus on &#8220;synchroniza=
tion use case&#8221; first.&nbsp; Then dig into pagination so that we&#8217=
;re not trying to talk to both at the same time.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">On the topic of synchronization, I think there are t=
wo common use cases:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"MsoListParagraph" style=3D"margin-left:-13.2pt;mso-list:l0 lev=
el1 lfo5">
<b>Constructing and enforcing Application authorization models</b> -&nbsp; =
An application (acting as a SCIM client) caches users/groups data from the =
IdP in order to present &#8220;user/group pickers&#8221; when presenting sc=
reens used to configure the application &nbsp;authorization
 rules (RBAC, Policy, or ACL).&nbsp; Also, when the application enforces au=
thorization, user and group data needs to be immediately available so that =
authorization decisions can be made quickly.
<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-left:-13.2pt=
;mso-list:l0 level1 lfo5">
<b>Identity Management and Governance systems</b> &#8211; implement a canon=
ical identity model&#8221; where all accounts and groups are represented.&n=
bsp; This model is used to build provisioning rules and calculate separatio=
n of duty violations, attestations, and approvals
 etc.&nbsp;&nbsp; Management-time evaluation of the model needs to be done =
efficiently without external calls to the SCIM service provider.&nbsp;
<o:p></o:p></li></ol>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Both of the above use cases, are client-cache use ca=
ses -- a &#8220;one-way&#8221; sync:&nbsp; a) download the initial results =
and, b) keep the results up to date with changes that are being made on the=
 SCIM Service provider. &nbsp;&nbsp;&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It think it could help us narrow down the list of su=
itable approaches if we could agree that &#8220;one-way&#8221; sync (keepin=
g a client-side cache up to date) is our target.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">--<o:p></o:p></p>
<p class=3D"MsoNormal">Matt &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> scim &lt;scim-bounces@ietf.org&gt; <b>O=
n Behalf Of </b>
Phil Hunt<br>
<b>Sent:</b> Friday, August 13, 2021 1:52 PM<br>
<b>To:</b> Pamela Dingle &lt;Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org=
&gt;<br>
<b>Cc:</b> scim@ietf.org<br>
<b>Subject:</b> Re: [scim] BoF Review and workshopping the Charter based on=
 SCIM IG call, Aug 4<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:solid #9C6500 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt">
<p class=3D"MsoNormal" style=3D"line-height:12.0pt;background:#FFEB9C"><b><=
span style=3D"font-size:10.0pt;color:#9C6500">CAUTION:</span></b><span styl=
e=3D"font-size:10.0pt;color:black"> This email originated from outside of t=
he organization. Do not follow guidance,
 click links, or open attachments unless you recognize the sender and know =
the content is safe.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Pam, <o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks for the notes. &nbsp;Apologies for not making=
 the last meeting.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Paging and Sync Comments:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In my conversations with Matt Peterson we both have =
the feeling that the request for &#8220;stateful&#8221; paging of results h=
as to do with clients wanting to do synchronization. The technical need is =
driven by memory limitations in clients. &nbsp;Matt,
 let me know if I am speaking out of turn, but this form of &#8220;paging&#=
8221; for synchronization and reconciliation is a &#8220;poor-mans&#8221; a=
pproach.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I would like to ask if there are other use-cases or =
need people have for stateful paging other than co-ordination and synchroni=
zation. If so, stateful paging may be worth pursuing given appropriate cave=
ats.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Given this, Synchronization/Co-ordination needs to b=
e explored at least in case of requirements as a charter item. &nbsp;In SCI=
M environments there are many cross-domain scenarios where items are not be=
ing replicated. However entity life-cycles
 need to be co-ordinated. &nbsp;I would like to see an approach that works =
on &#8220;changes&#8221; only rather than pulling full data sets. &nbsp;Thi=
s is an information minimization approach and minimizes data transfer. &nbs=
p; There are many possible technolgoies we could explore:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Security Event streams (publish/subscribe or event=
 bus). &nbsp;A stream can be explicit or contain simple &#8220;this resourc=
e has changed&#8221;.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Usage of pre-conditions to detect resource changes=
 (date and etag)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Change date query to detect changed resources (kin=
d of an evolution of ldap changelog)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Reversal of roles. &nbsp;Service provider acts as =
client to send changes back<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">* Others TBD<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Schemas:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Regarding Leif&#8217;s comments, I took him to mean =
he would ike to see servers not built on hard coded or otherwise fixed sche=
ma (e.g. POJOs). &nbsp;I didn&#8217;t take him to mean that there was proto=
col work to be done here. &nbsp; My recently published
<a href=3D"https://nam12.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F=
%2Fi2scim.io%2F&amp;data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff=
4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C6376448=
11626277847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ=
BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dqxy0%2BxCMe4vJ7A3HZ5hmAlEkzc=
zsvq52fOBsRfZ7h%2BY%3D&amp;reserved=3D0">
i2scim.io</a> open source implementation is an example of this.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">From the call I am not sure what was meant by &#8220=
;Discoverable schema is only useful for optional attributes&#8221;. &nbsp;I=
n the sense that a server should support Users and Groups, there&#8217;s no=
thing saying other schemas and resource types can&#8217;t be defined
 and optionally registered via IANA. &nbsp;In that sense, the /ResourceType=
s and /Schemas endpoints become very meaningful.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I think there is a higher level problem of interring=
 meaning beyond Attributes types and characteristics as well as resource ty=
pe definitions that may seem arbitrary. I think this is where the standard =
process is useful. &nbsp;Any publication
 process is going to help act as a reference for implementers to understand=
 purpose and meaning beyond raw data.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Phil Hunt<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">@independentid<o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"mailto:phil.hunt@independentid.com">phil.=
hunt@independentid.com</a><span style=3D"color:black"><o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">On Aug 13, 2021, at 5:36 AM, Pamela Dingle &lt;<a hr=
ef=3D"mailto:Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org">Pamela.Dingle=
=3D40microsoft.com@dmarc.ietf.org</a>&gt; wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Hi all,&nbsp;</span=
><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Apologies for the l=
ateness of this summary!&nbsp; &nbsp; This note talks through our discussio=
n last week on our BoF and on next steps, but the real meat here is the dec=
ision making that necessarily needs to move to
 be email-focused.&nbsp; &nbsp;Please give us your reactions to the topics =
below.&nbsp; &nbsp; Additionally,&nbsp;&nbsp;our summary of the meeeting, l=
inks to the meeting, and thoughts and goals moving forward are here:&nbsp;&=
nbsp;</span><a href=3D"https://nam12.safelinks.protection.outlook.com/?url=
=3Dhttps%3A%2F%2Fgithub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%=
2F2021%2F2021-08-04.md&amp;data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5=
d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C=
637644811626287844%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu=
MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3DNbBTKbHYd8E2X%2BnqvYA=
fPMUhZzP6pJIRNa4q%2Bbck8pA%3D&amp;reserved=3D0" target=3D"_blank" title=3D"=
Original URL: https://github.com/SCIM-Interest-Group/meetings/blob/main/202=
1/2021-08-04.md. Click or tap if you trust this link."><span style=3D"font-=
size:12.0pt">meetings/2021-08-04.md
 at main &middot; SCIM-Interest-Group/meetings (github.com)</span></a><span=
 style=3D"font-size:12.0pt">.&nbsp;Video of the meeting is available on You=
tube:&nbsp;</span><a href=3D"https://nam12.safelinks.protection.outlook.com=
/?url=3Dhttps%3A%2F%2Fyoutu.be%2FmsGCsG752PA&amp;data=3D04%7C01%7Cmatt.pete=
rson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1=
867ec606603%7C0%7C1%7C637644811626297841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC=
4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=
=3Dq5pABg2LL5A5%2FtK%2B5b2RONXNYJvHbvul%2FmIi6NIzwd0%3D&amp;reserved=3D0" t=
arget=3D"_blank" title=3D"Original URL: https://youtu.be/msGCsG752PA. Click=
 or tap if you trust this link."><span style=3D"font-size:12.0pt">https://y=
outu.be/msGCsG752PA</span></a><o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#201F1E">&nbsp;<o:p></o:p></spa=
n></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Three issues need s=
urfacing to the wider community, based on commentary in the BoF:</span><o:p=
></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Synchronization =
not a Charter Focus</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">While we have spoke=
n a lot in our interest group meetings about pagination, comments from Mort=
eza around synchronization sparked a conversation around the relationship b=
etween pagination and synchronization
 -- is it that pagination is so critical because large data set fetches are=
 the only way to do synchronization?&nbsp; &nbsp;The consensus from the gro=
up in the meeting was that yes, there is a relationship here, and while we =
definitely still think pagination is a critical
 topic, understanding the nature of our syncronization use cases could shed=
 light on why large data set handling is so critical for many.</span><o:p><=
/o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Fixed vs. Discov=
erable Schema</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Discussion of Leif'=
s comments in the BoF about lack of flexibility in current schema efforts r=
esulted&nbsp; the group suggested that we should look at what could be done=
 to better support discoverable schema.&nbsp;
 Can we make the discovery mechanism already in the spec more dynamic or mo=
re able to be part of a schema negotiation?</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Discussion on Ex=
ternal ID and Privileged Access</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">We didn't get a cha=
nce to discuss, but are looking for thoughts and discussion from the commun=
ity.&nbsp;&nbsp;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt">Moving towards I=
ETF Conformant Comms and Processes</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span class=3D"mark93ggdq4rb"><span style=3D"font-si=
ze:12.0pt">Nancy</span></span><span style=3D"font-size:12.0pt">&nbsp;<span =
class=3D"markn0rq63e6z">Cam</span>&nbsp;<span class=3D"mark2yn8vnlym">Winge=
t</span>&nbsp;(one of our BoF chairs) has been advising us
 on next steps and the discussion began on process.&nbsp; The group took a =
shot at running some consensus calls today in the meeting based on the abov=
e topics, you can see them below and we want your feedback, but going&nbsp;=
 chairs. Additionally&nbsp;<span class=3D"mark93ggdq4rb">Nancy</span>&nbsp;=
was
 very clear that the critical consensus mechanism needs to be the mailing l=
ist - so we will work to make sure those motions are properly followed.&nbs=
p;</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Please give us your=
 thoughts &amp; reactions to these two statements and their impact on the p=
roposed charter:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"color:#201=
F1E"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><b><span style=3D"font-si=
ze:12.0pt;color:#201F1E">Consensus call (9/11 within the call): &nbsp;We wi=
ll explore synchronization patterns and deliver a document describing what =
implementers are doing, with one focus being
 how large data sets are involved as an early deliverable</span></b><span s=
tyle=3D"color:#201F1E"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">&nbsp;</span><o:p><=
/o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><b><span style=3D"font-si=
ze:12.0pt;color:#201F1E">Consensus call (7/11 within the call) for &quot;in=
vestigating discoverable schema as part of our schema milestone&quot; deliv=
erable would be a document containing recommendations
 delivered to the WG</span></b><span style=3D"color:#201F1E"><o:p></o:p></s=
pan></p>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Cheers,<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Pam<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;font-family:&quot;Hel=
vetica&quot;,sans-serif">_______________________________________________<br=
>
scim mailing list<br>
</span><a href=3D"mailto:scim@ietf.org"><span style=3D"font-size:9.0pt;font=
-family:&quot;Helvetica&quot;,sans-serif">scim@ietf.org</span></a><span sty=
le=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,sans-serif"><br>
</span><a href=3D"https://nam12.safelinks.protection.outlook.com/?url=3Dhtt=
ps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cma=
tt.peterson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e43=
9c989c1867ec606603%7C0%7C1%7C637644811626307835%7CUnknown%7CTWFpbGZsb3d8eyJ=
WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;=
sdata=3DSkaa6SfAZRcFCpVgRW8vQ8DZXTVgrHYXlbB7stowng8%3D&amp;reserved=3D0"><s=
pan style=3D"font-size:9.0pt;font-family:&quot;Helvetica&quot;,sans-serif">=
https://www.ietf.org/mailman/listinfo/scim</span></a><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9MWHPR19MB0957namp_--


From nobody Wed Aug 18 05:51:39 2021
Return-Path: <Pamela.Dingle@microsoft.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 DAB753A17F9 for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 05:51:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=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 195pVddWL-pD for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 05:51:30 -0700 (PDT)
Received: from outbound.mail.eo.outlook.com (mail-oln040093003013.outbound.protection.outlook.com [40.93.3.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87AF83A17F7 for <scim@ietf.org>; Wed, 18 Aug 2021 05:51:30 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Y/WN8M5MMYg86pC6R93QlynjTyhqsj9vOcg6gpI162UK4yIa3MxbCgtpcX46SeVS/nrYC+tSpWOsZigVicQsNuEpMlO/Qny/ALLnxwS5FVSmrRnNaXQSUYmDSiRfNGDA+aGGgQ0O4cgpydJvoi9vAMZfpk/6dzn9rtlPs3k3bJg4J1jHOZVVS8Z9rrYAdO+uZzhugkDtfVTkllbYQpJOwLa+itmrZVupzmRlbLcAW4Hxx77+Gt02Jpuf3COzX481CL8JAl1Ibn1L9q0RdgqCuzhvGDtgJNlzJ3Kh+28VBuHDw00mPH7Oj8po8ukwDpEU4gZFyAnLn0zHdZFalwcrhA==
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;  bh=VCFjTk7Gr5XTrn/4M3p7B8Z1a58lgh/lCJNqRdG9drM=; b=oXJkw/fnWe6OYQfUJSD5CfAONlOrcIVExb3SP2IxCpw29GWKQgMKC4I8cDU6ir7N6uVE6MOQz1gdWEr73lBbjdVeMkwXeJ0npCUzuV7cLDvSrXTMO6C2X4eagPwgVkqu8hucOnhmRdrkRO1G+cjorYlikFTPFtRY9aHzbbWcoLGiX698BxtBOnaoL0j5b8JRS3CoN3o4rUHv/NOvq4T0eB6cV5lcZ5iuu14T2T3vh5oiBZci/L9DY7z2JRjUJVSzmnK/76tD8p4FzlZhGu14bxHsWDTVV9FEfvyC8CM5xIChGALKBcuoXzb8YEdm47sG15JDnVIssP71SNUKRY7DZA==
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=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VCFjTk7Gr5XTrn/4M3p7B8Z1a58lgh/lCJNqRdG9drM=; b=R9QinwM3N3Ms+NcrhkjBNRvnyO9UFA5AB3nC+ETa2nlO7ReWm6SwNV9WtCXwmgDcKOLzVB6gWvtoHfrCgHBxrPxJTRc3XX7W6DDsbWe2ycZK0gKfnerJ62vCL6o/vaRUHJfZGb/YLnxrJ3RgKaXPMoV4L3oop4XoVWPHAeSLelE=
Received: from BY5PR00MB0757.namprd00.prod.outlook.com (2603:10b6:a03:1dc::10) by SJ0PR00MB1176.namprd00.prod.outlook.com (2603:10b6:a03:359::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4475.0; Wed, 18 Aug 2021 12:51:27 +0000
Received: from BY5PR00MB0757.namprd00.prod.outlook.com ([fe80::e945:e923:665a:d0f4]) by BY5PR00MB0757.namprd00.prod.outlook.com ([fe80::e945:e923:665a:d0f4%8]) with mapi id 15.20.4475.000; Wed, 18 Aug 2021 12:51:27 +0000
From: Pamela Dingle <Pamela.Dingle@microsoft.com>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: SCIM IG Meeting: Today, next on Sept 1
Thread-Index: AQHXlC6Tcex+aYGcYki+gkwOq2szTg==
Date: Wed, 18 Aug 2021 12:51:27 +0000
Message-ID: <BY5PR00MB0757613418722B74AAE7EB60F6FF9@BY5PR00MB0757.namprd00.prod.outlook.com>
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_SetDate=2021-08-18T12:51:28.780Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 734ff7ae-ff7a-4407-de7f-08d96246e4f6
x-ms-traffictypediagnostic: SJ0PR00MB1176:
x-microsoft-antispam-prvs: <SJ0PR00MB1176C4A7436C6833DBFBEE41F6FF9@SJ0PR00MB1176.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mpQ/4hVvebMJcXqMfz3+JNL+grmEcEC3yhAkKjBiwmL7vr4ZpafLvSIQoth5d4EJ4fBBS6W5/V21i78n0xCQZLUkOS26Q9m0Hzi71uS1KEPclmMUIgEFXf0aVxNikNuopPxRzpD4XgW3lg5NUo7id+eCnZP8kDQH6jE2IRxWqjvlnsqu1quy308kooyRqjjK10v4+qWkITn6+IvB4zHIZsUGJxKoYAD4vdQGI0J4rGlBtRGe/26KaQy4JUWdV34SUIqeDSPraa9ucyOes9ndzL8ogUS4WHCeoi+4V29fRI56UHG9jymlE/0eUsBSS8DsLkbg3RR5fONLMHqq7EIrmsbPbBaE7MYIr+prwTi/rdlDCptNVi1W23BH/wINHlx4pLlhk/xMq8c0wy4nntC6EjlWBYTUgM0l9M9o/1PXtfUKvbGYvgKIPTeQ5br3Bvhk7HPIyRK8PC+YLFy4eP5zzihkZAVEs4l92GF+u+Lv3+VdZr/VRuWr1F6HHrTCXQ5w2ywRCTnXQjGhdchoUgen2kUt6xEQFokkq65edL5aYKsFg+ecXJzA+wOAaGs8TN6rjVgLtCEvVGhorgFDGAQOp4iLlXq29H0tDUzGt9SLCopi4UduBSgUvK4Q2YBj+ugMvICQh6m+gHGhJofvVzyNkSdC0SYvTDbUa9Sbm0Ul/P1qGDf6k0dYUs6+u0oH/yRMGtpTYKVSrLqcjx/11jzK9P1WOyMSKMXIJmjpYN1Z7gF7Xp6sx2adxoUFHDjV9F+wht4ngUuPKHnTunvz5l87fi0Y9l/XlKOailEA1tgbSv9n4qMVvOXcUTuttMNGMhg427DjytmHSUlk2bu5Sp/z3A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BY5PR00MB0757.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(10290500003)(55016002)(4744005)(52536014)(82950400001)(82960400001)(8990500004)(5660300002)(71200400001)(19627405001)(6506007)(76116006)(186003)(66446008)(64756008)(66556008)(66476007)(38070700005)(26005)(316002)(9686003)(7696005)(508600001)(66946007)(6916009)(21615005)(8936002)(8676002)(86362001)(33656002)(122000001)(38100700002)(166002)(2906002)(83380400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?PsROuVl/xqRWhwZEEnLAZzwCRqFoHaczjoARIDwtAcgCTOed7KHhJ74LLV?= =?iso-8859-1?Q?quyqJaXyHIhblLlp6jtWD+6HAhgqhRpeLMzSoC/uJdPCxB3Tqdj0gtyP0u?= =?iso-8859-1?Q?5ak/V3ujCU6sPIOlp99vRz7Hy+4BthPaa5TH3yhB6mb/+vDb4vEeABvXjQ?= =?iso-8859-1?Q?Ks5/tTQR04mWM6DBtxUw+ecy8BjXaVa4rMOb7z0n/qMMYycyaQhIHlQ5ak?= =?iso-8859-1?Q?s4iwvaFDTOUVrFI5YxBfVs8H01gBX/s+9+kVieli8WwpRuwbfGdU/nFEce?= =?iso-8859-1?Q?68bhfD4NMqdgrLFIe6uW9ILY+I7XS1Qa1OFSMvX7+o2hVZHF1BItatQlOp?= =?iso-8859-1?Q?cCVvYGHwkfTcXYXzOd0keBJZJu8oVzGWaPTtOZsLEFRwRffgW+ZhpIiHrq?= =?iso-8859-1?Q?Ddl4XbVnwAk3LiZREVatnKdwKuMWLDY3XlXIxlIIZ3Vqq9mR0/s7w3EMTC?= =?iso-8859-1?Q?VU8oFgqv14GtMk3MqQDtpZ2FHkouG1AHeMx0Hz5BuznDJoA2IBr1VApRsF?= =?iso-8859-1?Q?UKSlbEvwud2GcIPE0+lkbh6BurGZU31UZzGKK5A9k2L898gZbOemG7dlww?= =?iso-8859-1?Q?OjyVGcFEZJBgB9svngpPOnuNjrFW0XHGkll56MNTjp8/myy5AwdHXkzXmU?= =?iso-8859-1?Q?FigptNOeDRtO2mIz0wmHjsEm7UMOqz666BzR/6p7XS30JKv9CaSnOurT6X?= =?iso-8859-1?Q?p6PuZrUO+UmH6lXxucJK2dzHC3SqpfYOKdlfDtuTICBds9wS0DOdEklbLM?= =?iso-8859-1?Q?K4m19pMHDArPSFaSTQmlmwz7+t/PzyA8L6KfPz/qBzlVSAzBeP08IE7CTl?= =?iso-8859-1?Q?Y6DP5vtLXWcB6ylOQjeaSThyBbOE0GfiF4uMr4gbjYYU4CzTEtWnMI5Fki?= =?iso-8859-1?Q?fofIyNJ2XHt9MOEdz1/wY7tXfcjK8lWlIlwOxm8gO43lzYOuFuuYocS2FI?= =?iso-8859-1?Q?I8zkUD5Jp1JfilxviNCN9KIln4UPPx4OKwbH15XZQsOWi+JO5RJqEF1al1?= =?iso-8859-1?Q?+gn4ClDD6b8CqSIgeoZvnCcZEsXGEJdKTdnNZA/Yg3dt1SPHt1WwCq2hje?= =?iso-8859-1?Q?g2YpZD3dC5EST13IpBBHNXkl5q19B7VKkL0k06Mqp5XFolZNSjPfzRNq6X?= =?iso-8859-1?Q?EjQXplwrrW4kadddw81eB1RnoCN2Ay/6MkW+1uCk3pGF7oYWuwSh91u3h7?= =?iso-8859-1?Q?8yC6kHYzQ4BE7ZBaPyeXeCv2LBXD/w5ubrSBLZNtLn+n5Ro1cR6sUhSLiH?= =?iso-8859-1?Q?Lg8oeTjythIU+vO5nxgYQo0ZKy6POUURLInc7xjkKeFiBSBMKz6Sc8gLry?= =?iso-8859-1?Q?+Zsi9RDCUJboUntLKjchnweI2oKmffpUNJnGk82SZIEREfo=3D?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR00MB0757613418722B74AAE7EB60F6FF9BY5PR00MB0757namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BY5PR00MB0757.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 734ff7ae-ff7a-4407-de7f-08d96246e4f6
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Aug 2021 12:51:27.7177 (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: vRBr6ZuwmtZL7lvRxpyoF+OsIswWMk+0giC5O03NzSznxeua5NDAQG0sHmalixzbDYV6O0HoeSoO26XnU+3F0w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SJ0PR00MB1176
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/IB-nYj0mb9WwV5fEm3LUGpiwW_U>
Subject: [scim] SCIM IG Meeting: Today, next on Sept 1
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 18 Aug 2021 12:51:36 -0000

--_000_BY5PR00MB0757613418722B74AAE7EB60F6FF9BY5PR00MB0757namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Reminder that today's SCIM IG meeting is on at 3pm PT,  we're working towar=
ds tuning the charter.    September 1st is our next SCIM meeting, we meet o=
n the first and third Wednesday of every month and the calendar series can =
be viewed as HTML<https://outlook.live.com/calendar/published/00000000-0000=
-0000-0000-000000000000/25ef962b-555f-4781-b533-bfe7be451be8/cid-95C8043F86=
2EFECA/calendar.html> or as a .ics calendar link<https://outlook.live.com/o=
wa/calendar/00000000-0000-0000-0000-000000000000/25ef962b-555f-4781-b533-bf=
e7be451be8/cid-95C8043F862EFECA/calendar.ics>.

The teams link for the meeting is here<https://teams.microsoft.com/l/meetup=
-join/19%3ameeting_Y2QxYzU0NjEtN2ZjNi00MGQ1LWJkMzUtZmQxZjZlZGZiYWZi%40threa=
d.v2/0?context=3D%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011db47%22%=
2c%22Oid%22%3a%2285bc2986-6412-41c0-ab6d-98c80048fe64%22%7d>!  See you at 3=
pm PT.

Cheers,

Pamela

--_000_BY5PR00MB0757613418722B74AAE7EB60F6FF9BY5PR00MB0757namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Hi all,</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Reminder that today's SCIM IG meeting is on at 3pm PT,&nbsp; we're working =
towards tuning the charter.&nbsp; &nbsp; September 1st is our next SCIM mee=
ting, we meet on the first and third Wednesday of every month and the calen=
dar series can be viewed as
<a href=3D"https://outlook.live.com/calendar/published/00000000-0000-0000-0=
000-000000000000/25ef962b-555f-4781-b533-bfe7be451be8/cid-95C8043F862EFECA/=
calendar.html" title=3D"https://outlook.live.com/calendar/published/0000000=
0-0000-0000-0000-000000000000/25ef962b-555f-4781-b533-bfe7be451be8/cid-95C8=
043F862EFECA/calendar.html">
HTML</a> or as a <a href=3D"https://outlook.live.com/owa/calendar/00000000-=
0000-0000-0000-000000000000/25ef962b-555f-4781-b533-bfe7be451be8/cid-95C804=
3F862EFECA/calendar.ics" title=3D"https://outlook.live.com/owa/calendar/000=
00000-0000-0000-0000-000000000000/25ef962b-555f-4781-b533-bfe7be451be8/cid-=
95C8043F862EFECA/calendar.ics">
.ics calendar link</a>.&nbsp;&nbsp;</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
The teams link for the meeting is <a href=3D"https://teams.microsoft.com/l/=
meetup-join/19%3ameeting_Y2QxYzU0NjEtN2ZjNi00MGQ1LWJkMzUtZmQxZjZlZGZiYWZi%4=
0thread.v2/0?context=3D%7b%22Tid%22%3a%2272f988bf-86f1-41af-91ab-2d7cd011db=
47%22%2c%22Oid%22%3a%2285bc2986-6412-41c0-ab6d-98c80048fe64%22%7d" title=3D=
"https://teams.microsoft.com/l/meetup-join/19%3ameeting_Y2QxYzU0NjEtN2ZjNi0=
0MGQ1LWJkMzUtZmQxZjZlZGZiYWZi%40thread.v2/0?context=3D%7b%22Tid%22%3a%2272f=
988bf-86f1-41af-91ab-2d7cd011db47%22%2c%22Oid%22%3a%2285bc2986-6412-41c0-ab=
6d-98c80048fe64%22%7d">
here</a>!&nbsp; See you at 3pm PT.</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Cheers,</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
Pamela</div>
</body>
</html>

--_000_BY5PR00MB0757613418722B74AAE7EB60F6FF9BY5PR00MB0757namp_--


From nobody Wed Aug 18 05:56:21 2021
Return-Path: <wesleydunnington@pingidentity.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 C1F1B3A1825 for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 05:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.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 vs2mAyzYNN1D for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 05:56:13 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 B904C3A1820 for <scim@ietf.org>; Wed, 18 Aug 2021 05:56:12 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id b7so3028556edu.3 for <scim@ietf.org>; Wed, 18 Aug 2021 05:56:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=u1mGzP9rBDVcfjaagdqZfNiGZI+QLz8OmljkUEQkVQI=; b=fmeWn8et7Uxp6nLxR5dMjx+u7YkoLcPnza/iyN7XwQxy4E9qcmAny6lZkklblaP2Ma JeGvXRCTOxxzDp3Oi7t3iXT+nOo7YtGG/eu9aIDBHG//Jw0VSYG5G770Xdq1IBRPZq28 8fYrNnHU1FTgrYjV+3kWcNhnvr+WILKS+bi/WDTTpaGoIFWJ2r4gEW+PD+pv+R09wHfD 92pdEE36+K4LpWJWWw9iYwiP+FkfLz/lv+hBeJSLBNRCJCGFgfC4Tc2/WqPVDoEK+Z/Z FwhSENQ1DWIwn4Z/X7PRwOXc3wzGIPmf365GnO886ZhnrMP4ngePGtya1L6YYL085SZ9 m18Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=u1mGzP9rBDVcfjaagdqZfNiGZI+QLz8OmljkUEQkVQI=; b=I3ozMMMZe/aU/V8mjJwGuNbgi8DhBKwDF+SQ7VXU7j29z8S4xHewiv1HWvxcyx9Dek eLxU6Y0oCnF5459ovFaQn2h6831aRTHZqlIDDkfctQUF83+gEeYS+JXksFClvAKP/ktr TBpDWW7FzfDVvzMUSR5hSU05Kfj+y5/KXKxKyaCsKo6hxCx4wV+KQAJvO/Hf489nM1SQ y5Ztc1lL54LXAJwdJYSes0zoibKdr6kUpWTz/o9PVNwvEAeCrbW20TB/VQVci1z6B4O/ jpMk2Nv4TO8mz5m1KUxG2jFAPyfjuxBcFeUMx/JjFJ2E3UU3YmYn7/BG4jR2bvkvxG0i uDbA==
X-Gm-Message-State: AOAM532pPXzg+jwj1CvuWeXLsC7JSWhXpNVASP4EnnbXMnpR4QulieTs TYnUI1Eg23k+mZFcneQb/0/lH1AVhd5nV/1zEpjs4LMuTf8ZrClodoVgas6f34Z+/xCFv7cjUvU WX19+EQ8s8dqMVAmq0Q==
X-Google-Smtp-Source: ABdhPJyxqVf6fjQj2sLxySLesOapcAsjTvCuCoTiAsk1Ga4vUkXm3ZQ8HZBrZs2inioXpHtp0udxfIApI5pk/vt6ZnE=
X-Received: by 2002:aa7:c303:: with SMTP id l3mr10125179edq.245.1629291368446;  Wed, 18 Aug 2021 05:56:08 -0700 (PDT)
MIME-Version: 1.0
References: <BY5PR00MB07605CD725FD313DCE5BD78AF6FA9@BY5PR00MB0760.namprd00.prod.outlook.com> <D961D39B-72E0-463A-B7C0-9E366D0EDDD7@independentid.com> <MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9@MWHPR19MB0957.namprd19.prod.outlook.com>
In-Reply-To: <MWHPR19MB0957691C6351B9DAE73D5EC2E1FD9@MWHPR19MB0957.namprd19.prod.outlook.com>
From: Wesley Dunnington <wesleydunnington@pingidentity.com>
Date: Wed, 18 Aug 2021 08:55:57 -0400
Message-ID: <CAAnEc-19JHr6+i95wkyHuMo8s_JOUEo2ND_TO288TOPk6+8tvg@mail.gmail.com>
To: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
Cc: Phil Hunt <phil.hunt@independentid.com>, "scim@ietf.org" <scim@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040957e05c9d4f58c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/PbRqvzuKnlsI3nix0jWpvySZQZg>
Subject: Re: [scim] BoF Review and workshopping the Charter based on SCIM IG call, Aug 4
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 18 Aug 2021 12:56:19 -0000

--00000000000040957e05c9d4f58c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I don't know if its being thrown into the consideration set or not,
especially since Phil was one of the authors of the original draft, but the
use cases that had me excited about the pagination and filtering spec were
its enhanced querying and filtering capabilities, whether used as a
finer-grained synchronization mechanism, or simply as a query mechanism.

I just want to make sure those capabilities aren't being lost in the
synchronization discussion shuffle.

Best
Wes Dunnington

On Mon, Aug 16, 2021 at 2:07 PM Matt Peterson (mpeterso) <Matt.Peterson=3D
40oneidentity.com@dmarc.ietf.org> wrote:

> Phil,
>
>
>
> I agree.  I think that =E2=80=9Cclient-side caching=E2=80=9D (sync) of us=
ers and groups is
> a common use case for pagination because large results are generated not
> only the initial load of objects but also when trying to detect deletions
> (especially deletion of group memberships).  There must be a better (more
> efficient way) of handling this use case than polling with expensive
> queries.
>
>
>
> Like you, I=E2=80=99d really like to get people to post their pagination =
use cases
> so that we can categorize them.  I thought about posting to this mailing
> list with a follow up call for pagination use cases.
>
>
>
> But I also, I agree with what Parul said on the the Aug 4 call (from the
> meeting notes):
>
>
>
> *Parul: we do need cursor-based pagination, and that is unlikely to go
> away but it doesn't harm to first define the synchronization world and th=
en
> look at whether pagination needs to be enhanced=E2=80=A6*
>
>
>
> Parul=E2=80=99s suggestion on ordering the tasks is a good one.  It might=
 be
> useful to get a consensus on =E2=80=9Csynchronization use case=E2=80=9D f=
irst.  Then dig
> into pagination so that we=E2=80=99re not trying to talk to both at the s=
ame time.
>
>
>
> On the topic of synchronization, I think there are two common use cases:
>
>
>
>    1. *Constructing and enforcing Application authorization models* -  An
>    application (acting as a SCIM client) caches users/groups data from th=
e IdP
>    in order to present =E2=80=9Cuser/group pickers=E2=80=9D when presenti=
ng screens used to
>    configure the application  authorization rules (RBAC, Policy, or ACL).
>    Also, when the application enforces authorization, user and group data
>    needs to be immediately available so that authorization decisions can =
be
>    made quickly.
>    2. *Identity Management and Governance systems* =E2=80=93 implement a
>    canonical identity model=E2=80=9D where all accounts and groups are re=
presented.
>    This model is used to build provisioning rules and calculate separatio=
n of
>    duty violations, attestations, and approvals etc.   Management-time
>    evaluation of the model needs to be done efficiently without external =
calls
>    to the SCIM service provider.
>
>
>
> Both of the above use cases, are client-cache use cases -- a =E2=80=9Cone=
-way=E2=80=9D
> sync:  a) download the initial results and, b) keep the results up to dat=
e
> with changes that are being made on the SCIM Service provider.
>
>
>
> It think it could help us narrow down the list of suitable approaches if
> we could agree that =E2=80=9Cone-way=E2=80=9D sync (keeping a client-side=
 cache up to date)
> is our target.
>
>
>
> --
>
> Matt
>
>
>
> *From:* scim <scim-bounces@ietf.org> *On Behalf Of * Phil Hunt
> *Sent:* Friday, August 13, 2021 1:52 PM
> *To:* Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org>
> *Cc:* scim@ietf.org
> *Subject:* Re: [scim] BoF Review and workshopping the Charter based on
> SCIM IG call, Aug 4
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> follow guidance, click links, or open attachments unless you recognize th=
e
> sender and know the content is safe.
>
>
>
> Pam,
>
>
>
> Thanks for the notes.  Apologies for not making the last meeting.
>
>
>
>
>
> Paging and Sync Comments:
>
> In my conversations with Matt Peterson we both have the feeling that the
> request for =E2=80=9Cstateful=E2=80=9D paging of results has to do with c=
lients wanting to
> do synchronization. The technical need is driven by memory limitations in
> clients.  Matt, let me know if I am speaking out of turn, but this form o=
f
> =E2=80=9Cpaging=E2=80=9D for synchronization and reconciliation is a =E2=
=80=9Cpoor-mans=E2=80=9D approach.
>
>
>
> I would like to ask if there are other use-cases or need people have for
> stateful paging other than co-ordination and synchronization. If so,
> stateful paging may be worth pursuing given appropriate caveats.
>
>
>
> Given this, Synchronization/Co-ordination needs to be explored at least i=
n
> case of requirements as a charter item.  In SCIM environments there are
> many cross-domain scenarios where items are not being replicated. However
> entity life-cycles need to be co-ordinated.  I would like to see an
> approach that works on =E2=80=9Cchanges=E2=80=9D only rather than pulling=
 full data sets.
> This is an information minimization approach and minimizes data transfer.
> There are many possible technolgoies we could explore:
>
> * Security Event streams (publish/subscribe or event bus).  A stream can
> be explicit or contain simple =E2=80=9Cthis resource has changed=E2=80=9D=
.
>
> * Usage of pre-conditions to detect resource changes (date and etag)
>
> * Change date query to detect changed resources (kind of an evolution of
> ldap changelog)
>
> * Reversal of roles.  Service provider acts as client to send changes bac=
k
>
> * Others TBD
>
>
>
> Schemas:
>
> Regarding Leif=E2=80=99s comments, I took him to mean he would ike to see=
 servers
> not built on hard coded or otherwise fixed schema (e.g. POJOs).  I didn=
=E2=80=99t
> take him to mean that there was protocol work to be done here.   My
> recently published i2scim.io
> <https://nam12.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F%2Fi2sci=
m.io%2F&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff4a47121a2a08=
d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C637644811626277847%=
7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw=
iLCJXVCI6Mn0%3D%7C3000&sdata=3Dqxy0%2BxCMe4vJ7A3HZ5hmAlEkzczsvq52fOBsRfZ7h%=
2BY%3D&reserved=3D0>
> open source implementation is an example of this.
>
>
>
> From the call I am not sure what was meant by =E2=80=9CDiscoverable schem=
a is only
> useful for optional attributes=E2=80=9D.  In the sense that a server shou=
ld support
> Users and Groups, there=E2=80=99s nothing saying other schemas and resour=
ce types
> can=E2=80=99t be defined and optionally registered via IANA.  In that sen=
se, the
> /ResourceTypes and /Schemas endpoints become very meaningful.
>
>
>
> I think there is a higher level problem of interring meaning beyond
> Attributes types and characteristics as well as resource type definitions
> that may seem arbitrary. I think this is where the standard process is
> useful.  Any publication process is going to help act as a reference for
> implementers to understand purpose and meaning beyond raw data.
>
>
>
> Phil Hunt
>
> @independentid
>
> phil.hunt@independentid.com
>
>
>
>
>
>
>
> On Aug 13, 2021, at 5:36 AM, Pamela Dingle <
> Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org> wrote:
>
>
>
> Hi all,
>
> Apologies for the lateness of this summary!    This note talks through ou=
r
> discussion last week on our BoF and on next steps, but the real meat here
> is the decision making that necessarily needs to move to be email-focused=
.
>  Please give us your reactions to the topics below.    Additionally,  our
> summary of the meeeting, links to the meeting, and thoughts and goals
> moving forward are here:  meetings/2021-08-04.md at main =C2=B7
> SCIM-Interest-Group/meetings (github.com)
> <https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgith=
ub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%2F2021%2F2021-08-04.m=
d&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93=
e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C637644811626287844%7CUnkn=
own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV=
CI6Mn0%3D%7C3000&sdata=3DNbBTKbHYd8E2X%2BnqvYAfPMUhZzP6pJIRNa4q%2Bbck8pA%3D=
&reserved=3D0>. Video
> of the meeting is available on Youtube: https://youtu.be/msGCsG752PA
> <https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fyout=
u.be%2FmsGCsG752PA&data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff4=
a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C63764481=
1626297841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB=
TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3Dq5pABg2LL5A5%2FtK%2B5b2RONXNYJvHb=
vul%2FmIi6NIzwd0%3D&reserved=3D0>
>
>
>
> Three issues need surfacing to the wider community, based on commentary i=
n
> the BoF:
>
> *Synchronization not a Charter Focus*
>
> While we have spoken a lot in our interest group meetings about
> pagination, comments from Morteza around synchronization sparked a
> conversation around the relationship between pagination and synchronizati=
on
> -- is it that pagination is so critical because large data set fetches ar=
e
> the only way to do synchronization?   The consensus from the group in the
> meeting was that yes, there is a relationship here, and while we definite=
ly
> still think pagination is a critical topic, understanding the nature of o=
ur
> syncronization use cases could shed light on why large data set handling =
is
> so critical for many.
>
> *Fixed vs. Discoverable Schema*
>
> Discussion of Leif's comments in the BoF about lack of flexibility in
> current schema efforts resulted  the group suggested that we should look =
at
> what could be done to better support discoverable schema.  Can we make th=
e
> discovery mechanism already in the spec more dynamic or more able to be
> part of a schema negotiation?
>
> *Discussion on External ID and Privileged Access*
>
> We didn't get a chance to discuss, but are looking for thoughts and
> discussion from the community.
>
> *Moving towards IETF Conformant Comms and Processes*
>
> Nancy Cam Winget (one of our BoF chairs) has been advising us on next
> steps and the discussion began on process.  The group took a shot at
> running some consensus calls today in the meeting based on the above
> topics, you can see them below and we want your feedback, but going
> chairs. Additionally Nancy was very clear that the critical consensus
> mechanism needs to be the mailing list - so we will work to make sure tho=
se
> motions are properly followed.
>
> Please give us your thoughts & reactions to these two statements and thei=
r
> impact on the proposed charter:
>
>
>
> *Consensus call (9/11 within the call):  We will explore synchronization
> patterns and deliver a document describing what implementers are doing,
> with one focus being how large data sets are involved as an early
> deliverable*
>
>
>
> *Consensus call (7/11 within the call) for "investigating discoverable
> schema as part of our schema milestone" deliverable would be a document
> containing recommendations delivered to the WG*
>
> Cheers,
>
>
>
> Pam
>
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
> <https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
ietf.org%2Fmailman%2Flistinfo%2Fscim&data=3D04%7C01%7Cmatt.peterson%40quest=
.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%=
7C0%7C1%7C637644811626307835%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC=
JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3DSkaa6SfAZRcFCpV=
gRW8vQ8DZXTVgrHYXlbB7stowng8%3D&reserved=3D0>
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>


--=20
<https://www.pingidentity.com>[image: Ping Identity]
<https://www.pingidentity.com>
Wesley Dunnington
Senior Director Architecture
 wesleydunnington@pingidentity.com

c: 508-254-5475
Connect with us: [image: Glassdoor logo]
<https://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11=
,24.htm>
[image:
LinkedIn logo] <https://www.linkedin.com/company/21870> [image: twitter
logo] <https://twitter.com/pingidentity> [image: facebook logo]
<https://www.facebook.com/pingidentitypage> [image: youtube logo]
<https://www.youtube.com/user/PingIdentityTV> [image: Blog logo]
<https://www.pingidentity.com/en/blog.html>
<https://www.google.com/url?q=3Dhttps://www.pingidentity.com/content/dam/pi=
ng-6-2-assets/Assets/faqs/en/consumer-attitudes-post-breach-era-3375.pdf?id=
%3Db6322a80-f285-11e3-ac10-0800200c9a66&source=3Dgmail&ust=3D15416936085260=
00&usg=3DAFQjCNGBl5cPHCUAVKGZ_NnpuFj5PHGSUQ>
<https://www.pingidentity.com/en/events/d/identify-2019.html>
<https://www.pingidentity.com/content/dam/ping-6-2-assets/Assets/Misc/en/34=
64-consumersurvey-execsummary.pdf>
<https://www.pingidentity.com/en/events/e/rsa.html>
<https://www.pingidentity.com/en/events/e/rsa.html>
<https://www.gartner.com/reviews/vendor/write/ping-identity/?utm_content=3D=
vlp-write&refVal=3Dvlp-ping-identity-32202&utm_campaign=3Dvendor&utm_source=
=3Dping-identity&utm_medium=3Dweb&arwol=3Dfalse>
<https://www.gartner.com/reviews/vendor/write/ping-identity/?utm_content=3D=
vlp-write&refVal=3Dvlp-ping-identity-32202&utm_campaign=3Dvendor&utm_source=
=3Dping-identity&utm_medium=3Dweb&arwol=3Dfalse>

--=20
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged=
=20
material for the sole use of the intended recipient(s). Any review, use,=20
distribution or disclosure by others is strictly prohibited.=C2=A0 If you h=
ave=20
received this communication in error, please notify the sender immediately=
=20
by e-mail and delete the message and any file attachments from your=20
computer. Thank you._

--00000000000040957e05c9d4f58c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t know if its being thrown into the consideratio=
n set or not, especially since Phil was one of the authors of the original =
draft, but the use cases that had me excited about the pagination and filte=
ring spec were its enhanced querying and filtering capabilities, whether us=
ed as a finer-grained synchronization mechanism, or simply as a query mecha=
nism.=C2=A0<div><br></div><div>I just want to make sure those capabilities=
=C2=A0aren&#39;t being lost in the synchronization=C2=A0discussion shuffle.=
=C2=A0</div><div><br></div><div>Best</div><div>Wes Dunnington</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, =
Aug 16, 2021 at 2:07 PM Matt Peterson (mpeterso) &lt;Matt.Peterson=3D<a hre=
f=3D"mailto:40oneidentity.com@dmarc.ietf.org">40oneidentity.com@dmarc.ietf.=
org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-3304768218986609388WordSection1">
<p class=3D"MsoNormal">Phil, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I agree.=C2=A0 I think that =E2=80=9Cclient-side cac=
hing=E2=80=9D (sync) of users and groups is a common use case for paginatio=
n because large results are generated not only the initial load of objects =
but also when trying to detect deletions (especially deletion
 of group memberships).=C2=A0 There must be a better (more efficient way) o=
f handling this use case than polling with expensive queries.<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Like you, I=E2=80=99d really like to get people to p=
ost their pagination use cases so that we can categorize them.=C2=A0 I thou=
ght about posting to this mailing list with a follow up call for pagination=
 use cases.=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">But I also, I agree with what Parul said on the the =
Aug 4 call (from the meeting notes):<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in"><i>Parul: we do need cur=
sor-based pagination, and that is unlikely to go away but it doesn&#39;t ha=
rm to first define the synchronization world and then look at whether pagin=
ation needs to be enhanced=E2=80=A6<u></u><u></u></i></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Parul=E2=80=99s suggestion on ordering the tasks is =
a good one.=C2=A0 It might be useful to get a consensus on =E2=80=9Csynchro=
nization use case=E2=80=9D first.=C2=A0 Then dig into pagination so that we=
=E2=80=99re not trying to talk to both at the same time.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">On the topic of synchronization, I think there are t=
wo common use cases:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"gmail-m_-3304768218986609388MsoListParagraph">
<b>Constructing and enforcing Application authorization models</b> -=C2=A0 =
An application (acting as a SCIM client) caches users/groups data from the =
IdP in order to present =E2=80=9Cuser/group pickers=E2=80=9D when presentin=
g screens used to configure the application =C2=A0authorization
 rules (RBAC, Policy, or ACL).=C2=A0 Also, when the application enforces au=
thorization, user and group data needs to be immediately available so that =
authorization decisions can be made quickly.
<u></u><u></u></li><li class=3D"gmail-m_-3304768218986609388MsoListParagrap=
h">
<b>Identity Management and Governance systems</b> =E2=80=93 implement a can=
onical identity model=E2=80=9D where all accounts and groups are represente=
d.=C2=A0 This model is used to build provisioning rules and calculate separ=
ation of duty violations, attestations, and approvals
 etc.=C2=A0=C2=A0 Management-time evaluation of the model needs to be done =
efficiently without external calls to the SCIM service provider.=C2=A0
<u></u><u></u></li></ol>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Both of the above use cases, are client-cache use ca=
ses -- a =E2=80=9Cone-way=E2=80=9D sync:=C2=A0 a) download the initial resu=
lts and, b) keep the results up to date with changes that are being made on=
 the SCIM Service provider. =C2=A0=C2=A0=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">It think it could help us narrow down the list of su=
itable approaches if we could agree that =E2=80=9Cone-way=E2=80=9D sync (ke=
eping a client-side cache up to date) is our target.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">--<u></u><u></u></p>
<p class=3D"MsoNormal">Matt =C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> scim &lt;<a href=3D"mailto:scim-bounces=
@ietf.org" target=3D"_blank">scim-bounces@ietf.org</a>&gt; <b>On Behalf Of =
</b>
Phil Hunt<br>
<b>Sent:</b> Friday, August 13, 2021 1:52 PM<br>
<b>To:</b> Pamela Dingle &lt;Pamela.Dingle=3D<a href=3D"mailto:40microsoft.=
com@dmarc.ietf.org" target=3D"_blank">40microsoft.com@dmarc.ietf.org</a>&gt=
;<br>
<b>Cc:</b> <a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org=
</a><br>
<b>Subject:</b> Re: [scim] BoF Review and workshopping the Charter based on=
 SCIM IG call, Aug 4<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:1pt solid rgb(156,101,0);padding:2pt">
<p class=3D"MsoNormal" style=3D"line-height:12pt;background:rgb(255,235,156=
)"><b><span style=3D"font-size:10pt;color:rgb(156,101,0)">CAUTION:</span></=
b><span style=3D"font-size:10pt;color:black"> This email originated from ou=
tside of the organization. Do not follow guidance,
 click links, or open attachments unless you recognize the sender and know =
the content is safe.<u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Pam, <u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks for the notes.=C2=A0 Apologies for not making=
 the last meeting.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Paging and Sync Comments:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In my conversations with Matt Peterson we both have =
the feeling that the request for =E2=80=9Cstateful=E2=80=9D paging of resul=
ts has to do with clients wanting to do synchronization. The technical need=
 is driven by memory limitations in clients.=C2=A0 Matt,
 let me know if I am speaking out of turn, but this form of =E2=80=9Cpaging=
=E2=80=9D for synchronization and reconciliation is a =E2=80=9Cpoor-mans=E2=
=80=9D approach.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I would like to ask if there are other use-cases or =
need people have for stateful paging other than co-ordination and synchroni=
zation. If so, stateful paging may be worth pursuing given appropriate cave=
ats.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Given this, Synchronization/Co-ordination needs to b=
e explored at least in case of requirements as a charter item.=C2=A0 In SCI=
M environments there are many cross-domain scenarios where items are not be=
ing replicated. However entity life-cycles
 need to be co-ordinated.=C2=A0 I would like to see an approach that works =
on =E2=80=9Cchanges=E2=80=9D only rather than pulling full data sets.=C2=A0=
 This is an information minimization approach and minimizes data transfer. =
=C2=A0 There are many possible technolgoies we could explore:<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">* Security Event streams (publish/subscribe or event=
 bus).=C2=A0 A stream can be explicit or contain simple =E2=80=9Cthis resou=
rce has changed=E2=80=9D.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">* Usage of pre-conditions to detect resource changes=
 (date and etag)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">* Change date query to detect changed resources (kin=
d of an evolution of ldap changelog)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">* Reversal of roles.=C2=A0 Service provider acts as =
client to send changes back<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">* Others TBD<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Schemas:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Regarding Leif=E2=80=99s comments, I took him to mea=
n he would ike to see servers not built on hard coded or otherwise fixed sc=
hema (e.g. POJOs).=C2=A0 I didn=E2=80=99t take him to mean that there was p=
rotocol work to be done here. =C2=A0 My recently published
<a href=3D"https://nam12.safelinks.protection.outlook.com/?url=3Dhttp%3A%2F=
%2Fi2scim.io%2F&amp;data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5d35b1ff=
4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C6376448=
11626277847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ=
BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dqxy0%2BxCMe4vJ7A3HZ5hmAlEkzc=
zsvq52fOBsRfZ7h%2BY%3D&amp;reserved=3D0" target=3D"_blank">
i2scim.io</a> open source implementation is an example of this.<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">From the call I am not sure what was meant by =E2=80=
=9CDiscoverable schema is only useful for optional attributes=E2=80=9D.=C2=
=A0 In the sense that a server should support Users and Groups, there=E2=80=
=99s nothing saying other schemas and resource types can=E2=80=99t be defin=
ed
 and optionally registered via IANA.=C2=A0 In that sense, the /ResourceType=
s and /Schemas endpoints become very meaningful.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think there is a higher level problem of interring=
 meaning beyond Attributes types and characteristics as well as resource ty=
pe definitions that may seem arbitrary. I think this is where the standard =
process is useful.=C2=A0 Any publication
 process is going to help act as a reference for implementers to understand=
 purpose and meaning beyond raw data.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Phil Hunt<u></u><u></u><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">@independentid<u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"mailto:phil.hunt@independentid.com" targe=
t=3D"_blank">phil.hunt@independentid.com</a><span style=3D"color:black"><u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><u></u>=C2=A0<u></u></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><u></u>=C2=A0<u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<p class=3D"MsoNormal">On Aug 13, 2021, at 5:36 AM, Pamela Dingle &lt;<a hr=
ef=3D"mailto:Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org" target=3D"_bla=
nk">Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org</a>&gt; wrote:<u></u><u>=
</u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Hi all,=C2=A0</span><=
u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Apologies for the lat=
eness of this summary!=C2=A0 =C2=A0 This note talks through our discussion =
last week on our BoF and on next steps, but the real meat here is the decis=
ion making that necessarily needs to move to
 be email-focused.=C2=A0 =C2=A0Please give us your reactions to the topics =
below.=C2=A0 =C2=A0 Additionally,=C2=A0=C2=A0our summary of the meeeting, l=
inks to the meeting, and thoughts and goals moving forward are here:=C2=A0=
=C2=A0</span><a href=3D"https://nam12.safelinks.protection.outlook.com/?url=
=3Dhttps%3A%2F%2Fgithub.com%2FSCIM-Interest-Group%2Fmeetings%2Fblob%2Fmain%=
2F2021%2F2021-08-04.md&amp;data=3D04%7C01%7Cmatt.peterson%40quest.com%7C6d5=
d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C=
637644811626287844%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2lu=
MzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3DNbBTKbHYd8E2X%2BnqvYA=
fPMUhZzP6pJIRNa4q%2Bbck8pA%3D&amp;reserved=3D0" title=3D"Original URL: http=
s://github.com/SCIM-Interest-Group/meetings/blob/main/2021/2021-08-04.md. C=
lick or tap if you trust this link." target=3D"_blank"><span style=3D"font-=
size:12pt">meetings/2021-08-04.md
 at main =C2=B7 SCIM-Interest-Group/meetings (github.com)</span></a><span s=
tyle=3D"font-size:12pt">.=C2=A0Video of the meeting is available on Youtube=
:=C2=A0</span><a href=3D"https://nam12.safelinks.protection.outlook.com/?ur=
l=3Dhttps%3A%2F%2Fyoutu.be%2FmsGCsG752PA&amp;data=3D04%7C01%7Cmatt.peterson=
%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e439c989c1867e=
c606603%7C0%7C1%7C637644811626297841%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj=
AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dq5p=
ABg2LL5A5%2FtK%2B5b2RONXNYJvHbvul%2FmIi6NIzwd0%3D&amp;reserved=3D0" title=
=3D"Original URL: https://youtu.be/msGCsG752PA. Click or tap if you trust t=
his link." target=3D"_blank"><span style=3D"font-size:12pt">https://youtu.b=
e/msGCsG752PA</span></a><u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(32,31,30)">=C2=A0<u></u><u>=
</u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Three issues need sur=
facing to the wider community, based on commentary in the BoF:</span><u></u=
><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt">Synchronization no=
t a Charter Focus</span></b><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">While we have spoken =
a lot in our interest group meetings about pagination, comments from Mortez=
a around synchronization sparked a conversation around the relationship bet=
ween pagination and synchronization
 -- is it that pagination is so critical because large data set fetches are=
 the only way to do synchronization?=C2=A0 =C2=A0The consensus from the gro=
up in the meeting was that yes, there is a relationship here, and while we =
definitely still think pagination is a critical
 topic, understanding the nature of our syncronization use cases could shed=
 light on why large data set handling is so critical for many.</span><u></u=
><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt">Fixed vs. Discover=
able Schema</span></b><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Discussion of Leif&#3=
9;s comments in the BoF about lack of flexibility in current schema efforts=
 resulted=C2=A0 the group suggested that we should look at what could be do=
ne to better support discoverable schema.=C2=A0
 Can we make the discovery mechanism already in the spec more dynamic or mo=
re able to be part of a schema negotiation?</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt">Discussion on Exte=
rnal ID and Privileged Access</span></b><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">We didn&#39;t get a c=
hance to discuss, but are looking for thoughts and discussion from the comm=
unity.=C2=A0=C2=A0</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt">Moving towards IET=
F Conformant Comms and Processes</span></b><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span class=3D"gmail-m_-3304768218986609388mark93ggd=
q4rb"><span style=3D"font-size:12pt">Nancy</span></span><span style=3D"font=
-size:12pt">=C2=A0<span class=3D"gmail-m_-3304768218986609388markn0rq63e6z"=
>Cam</span>=C2=A0<span class=3D"gmail-m_-3304768218986609388mark2yn8vnlym">=
Winget</span>=C2=A0(one of our BoF chairs) has been advising us
 on next steps and the discussion began on process.=C2=A0 The group took a =
shot at running some consensus calls today in the meeting based on the abov=
e topics, you can see them below and we want your feedback, but going=C2=A0=
 chairs. Additionally=C2=A0<span class=3D"gmail-m_-3304768218986609388mark9=
3ggdq4rb">Nancy</span>=C2=A0was
 very clear that the critical consensus mechanism needs to be the mailing l=
ist - so we will work to make sure those motions are properly followed.=C2=
=A0</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Please give us your t=
houghts &amp; reactions to these two statements and their impact on the pro=
posed charter:</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><span style=3D"color:rgb(=
32,31,30)"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><b><span style=3D"font-si=
ze:12pt;color:rgb(32,31,30)">Consensus call (9/11 within the call): =C2=A0W=
e will explore synchronization patterns and deliver a document describing w=
hat implementers are doing, with one focus being
 how large data sets are involved as an early deliverable</span></b><span s=
tyle=3D"color:rgb(32,31,30)"><u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">=C2=A0</span><u></u><=
u></u></p>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<div>
<p class=3D"MsoNormal" style=3D"background:white"><b><span style=3D"font-si=
ze:12pt;color:rgb(32,31,30)">Consensus call (7/11 within the call) for &quo=
t;investigating discoverable schema as part of our schema milestone&quot; d=
eliverable would be a document containing recommendations
 delivered to the WG</span></b><span style=3D"color:rgb(32,31,30)"><u></u><=
u></u></span></p>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Cheers,<u></u><u></u>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt"><u></u>=C2=A0<u></u><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt">Pam<u></u><u></u></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt"><u></u>=C2=A0<u></u><=
/span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:9pt;font-family:Helvetica,s=
ans-serif">_______________________________________________<br>
scim mailing list<br>
</span><a href=3D"mailto:scim@ietf.org" target=3D"_blank"><span style=3D"fo=
nt-size:9pt;font-family:Helvetica,sans-serif">scim@ietf.org</span></a><span=
 style=3D"font-size:9pt;font-family:Helvetica,sans-serif"><br>
</span><a href=3D"https://nam12.safelinks.protection.outlook.com/?url=3Dhtt=
ps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cma=
tt.peterson%40quest.com%7C6d5d35b1ff4a47121a2a08d95e93e7e7%7C91c369b51c9e43=
9c989c1867ec606603%7C0%7C1%7C637644811626307835%7CUnknown%7CTWFpbGZsb3d8eyJ=
WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;=
sdata=3DSkaa6SfAZRcFCpVgRW8vQ8DZXTVgrHYXlbB7stowng8%3D&amp;reserved=3D0" ta=
rget=3D"_blank"><span style=3D"font-size:9pt;font-family:Helvetica,sans-ser=
if">https://www.ietf.org/mailman/listinfo/scim</span></a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>

_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/scim</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr">  <div style=3D"padding:0px;mar=
gin:0px">    <table style=3D"border-collapse:collapse;padding:0px;margin:0p=
x">			<tbody><tr>				<td style=3D"width:113px">					<a href=3D"https://www.=
pingidentity.com" target=3D"_blank"></a><a href=3D"https://www.pingidentity=
.com" target=3D"_blank"><img alt=3D"Ping Identity" src=3D"https://www.pingi=
dentity.com/content/dam/pic/images/misc/signature/ping-logo.png"></a>				</=
td>				<td>					<table>												<tbody><tr>			        <td style=3D"verti=
cal-align:top">				        <span style=3D"color:rgb(230,29,60);display:inli=
ne-block;margin-bottom:3px;font-family:arial,helvetica,sans-serif;font-weig=
ht:bold;font-size:14px">Wesley Dunnington</span>								<br><span style=3D"=
font-family:arial,helvetica,sans-serif;font-size:14px;display:inline-block;=
margin-bottom:3px"><font color=3D"#000000">Senior Director Architecture<br>=
=C2=A0</font><a href=3D"mailto:wesleydunnington@pingidentity.com" target=3D=
"_blank">wesleydunnington@pingidentity.com</a></span>								<br>								<s=
pan style=3D"color:rgb(0,0,0);display:inline-block;margin-bottom:2px;font-f=
amily:arial,helvetica,sans-serif;font-weight:normal;font-size:14px">							=
	</span>								<br>								<span style=3D"color:rgb(0,0,0);display:inline-=
block;margin-bottom:2px;font-family:arial,helvetica,sans-serif;font-weight:=
normal;font-size:14px">								c: 508-254-5475</span>							</td>			      <=
/tr>					</tbody></table>				</td>			</tr>			<tr>				        <td colspan=3D=
"2">          <table style=3D"border-collapse:collapse;border:none;margin:8=
px 0px 0px;width:100%">          	<tbody><tr style=3D"height:40px;border-to=
p:1px solid rgb(211,211,211);border-bottom:1px solid rgb(211,211,211)">    =
          <td style=3D"font-family:arial,helvetica,sans-serif;font-size:14p=
x;font-weight:bold;color:rgb(64,71,75)">Connect with us: </td>             =
 <td style=3D"padding:4px 0px 0px 20px">                <a href=3D"https://=
www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm" =
style=3D"text-decoration:none;margin-right:16px" title=3D"Ping on Glassdoor=
" target=3D"_blank"><img src=3D"https://www.pingidentity.com/content/dam/pi=
c/images/misc/signature/social-glassdoor.png" style=3D"border: none; margin=
: 0px;" alt=3D"Glassdoor logo"></a>										<a href=3D"https://www.linkedi=
n.com/company/21870" style=3D"text-decoration:none;margin-right:16px" title=
=3D"Ping on LinkedIn" target=3D"_blank"><img src=3D"https://www.pingidentit=
y.com/content/dam/pic/images/misc/signature/social-linkedin.png" style=3D"b=
order: none; margin: 0px;" alt=3D"LinkedIn logo"></a>                      =
                  <a href=3D"https://twitter.com/pingidentity" style=3D"tex=
t-decoration:none;margin-right:16px" title=3D"Ping on Twitter" target=3D"_b=
lank"><img src=3D"https://www.pingidentity.com/content/dam/pic/images/misc/=
signature/social-twitter.png" style=3D"border: none; margin: 0px;" alt=3D"t=
witter logo"></a>										<a href=3D"https://www.facebook.com/pingidentity=
page" style=3D"text-decoration:none;margin-right:16px" title=3D"Ping on Fac=
ebook" target=3D"_blank"><img src=3D"https://www.pingidentity.com/content/d=
am/pic/images/misc/signature/social-facebook.png" style=3D"border: none; ma=
rgin: 0px;" alt=3D"facebook logo"></a>								<a href=3D"https://www.youtub=
e.com/user/PingIdentityTV" style=3D"text-decoration:none;margin-right:16px"=
 title=3D"Ping on Youtube" target=3D"_blank"><img src=3D"https://www.pingid=
entity.com/content/dam/pic/images/misc/signature/social-youtube.png" style=
=3D"border: none; margin: 0px 0px 3px;" alt=3D"youtube logo"></a>          =
                                              <a href=3D"https://www.pingid=
entity.com/en/blog.html" style=3D"text-decoration:none;margin-right:16px" t=
itle=3D"Ping Blog" target=3D"_blank"><img src=3D"https://www.pingidentity.c=
om/content/dam/pic/images/misc/signature/social-blog.png" style=3D"border: =
none; margin: 0px;" alt=3D"Blog logo"></a>															</td>            <=
/tr>          </tbody></table>				</td>      </tr>    </tbody></table><a hr=
ef=3D"https://www.google.com/url?q=3Dhttps://www.pingidentity.com/content/d=
am/ping-6-2-assets/Assets/faqs/en/consumer-attitudes-post-breach-era-3375.p=
df?id%3Db6322a80-f285-11e3-ac10-0800200c9a66&amp;source=3Dgmail&amp;ust=3D1=
541693608526000&amp;usg=3DAFQjCNGBl5cPHCUAVKGZ_NnpuFj5PHGSUQ" target=3D"_bl=
ank"></a><a href=3D"https://www.pingidentity.com/en/events/d/identify-2019.=
html" target=3D"_blank"></a><a href=3D"https://www.pingidentity.com/content=
/dam/ping-6-2-assets/Assets/Misc/en/3464-consumersurvey-execsummary.pdf" ta=
rget=3D"_blank"></a><a href=3D"https://www.pingidentity.com/en/events/e/rsa=
.html" target=3D"_blank"></a><a href=3D"https://www.pingidentity.com/en/eve=
nts/e/rsa.html" target=3D"_blank"></a><a href=3D"https://www.gartner.com/re=
views/vendor/write/ping-identity/?utm_content=3Dvlp-write&amp;refVal=3Dvlp-=
ping-identity-32202&amp;utm_campaign=3Dvendor&amp;utm_source=3Dping-identit=
y&amp;utm_medium=3Dweb&amp;arwol=3Dfalse" target=3D"_blank"></a><a href=3D"=
https://www.gartner.com/reviews/vendor/write/ping-identity/?utm_content=3Dv=
lp-write&amp;refVal=3Dvlp-ping-identity-32202&amp;utm_campaign=3Dvendor&amp=
;utm_source=3Dping-identity&amp;utm_medium=3Dweb&amp;arwol=3Dfalse" target=
=3D"_blank"><img src=3D"https://www.pingidentity.com/content/dam/ping-6-2-a=
ssets/images/misc/emailSignature/2020/ReviewPing-EmailSignature.jpg"></a>  =
</div><div style=3D"padding:0px;margin:0px"><br></div></div></div>

<br>
<i style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:ba=
seline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-=
ui,-apple-system,system-ui,&quot;Segoe UI&quot;,Roboto,Oxygen-Sans,Ubuntu,C=
antarell,&quot;Helvetica Neue&quot;,Arial,sans-serif;color:rgb(85,85,85)"><=
span style=3D"margin:0px;padding:0px;border:0px;outline:0px;vertical-align:=
baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,=
-apple-system,BlinkMacSystemFont,&quot;Segoe UI&quot;,Roboto,Oxygen-Sans,Ub=
untu,Cantarell,&quot;Helvetica Neue&quot;,Arial,sans-serif;font-weight:600"=
><font size=3D"2">CONFIDENTIALITY NOTICE: This email may contain confidenti=
al and privileged material for the sole use of the intended recipient(s). A=
ny review, use, distribution or disclosure by others is strictly prohibited=
.=C2=A0 If you have received this communication in error, please notify the=
 sender immediately by e-mail and delete the message and any file attachmen=
ts from your computer. Thank you.</font></span></i>
--00000000000040957e05c9d4f58c--


From nobody Wed Aug 18 07:34:39 2021
Return-Path: <mayer@pdmconsulting.net>
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 6A04B3A1CBD for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 07:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 bFTDHCXch_qM for <scim@ietfa.amsl.com>; Wed, 18 Aug 2021 07:34:31 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD28B3A1CBC for <scim@ietf.org>; Wed, 18 Aug 2021 07:34:26 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GqVlg04KlzMNC2 for <scim@ietf.org>; Wed, 18 Aug 2021 14:34:22 +0000 (UTC)
To: SCIM WG <scim@ietf.org>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net>
Date: Wed, 18 Aug 2021 10:34:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/_mYeGVazInERgd-C5Ax02Xb_XAw>
Subject: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 18 Aug 2021 14:34:38 -0000

I decided that this needs it's own thread and not be part of the meeting =

minutes.

I have had a great deal of experience dealing with the user account=20
synchronization problem. Here's my view of the problems.

I will be calling one system Management Server and the other system=20
Application Server. I found client/server labels confusing. The=20
Management Server is what I am defining to be the server that sends=20
updates to add/update/remove users and groups to the Application server=20
whose account, groups and access permissions are being managed.

First some definitions of user accounts. There are usually more than one =

of each of these:
1. Builtin accounts
2. Special-purpose accounts
3. Employee
4. Contractor
5. Agent
6. Customer

There may be more.

1. Builtin accounts: These are accounts that applications have and there =

may be more than one. There is always an admin account which can do=20
anything, for example the administrator account in Active Directory or a =

database admin account. The application may have more accounts for other =

purposes.

2. Special-purpose accounts: These may be set up to provide access to=20
other applications, for example a SCIM request to a SCIM REST API should =

be handled by a special account which cannot be used to login via a UI=20
interface and only be able to perform certain functions. In addition=20
there may be accounts set up to listen for topics or queues on a message =

queue among other possibilities. Keeping separate accounts like this are =

important for tracking in logs and applications.

3. Employee: These are accounts that employees may login to the applicati=
on.

4. Contractors: These accounts that a contractor performing work for the =

company may use to log into an application. Unlike Employee accounts=20
these would have an expiration date.

5. Agent: Accounts like this are for external users who may need to=20
manage information for their own customers. An example of this is an=20
insurance agent logging in to handle an insurance policy for their client=
s.

6. Customers: These are where the customers are using the application=20
directly. For a bank it's likely to be millions of customers. The=20
management platform should not be involved in managing these accounts.

Let's now look at a few example applications.

1. Helpdesk
All employees and contractors will need to be able to log into a=20
helpdesk application and enter tickets. This means loading information=20
about all employees and contractors. For a company with only 1000=20
employees that's manageable. For a company with 100K employees, it's a=20
bigger challenge.

2. Customer Support
Only employees or contractors in the department providing customer=20
support need access plus a few other employees. In addition identified=20
customers may need accounts.

3. Expenses
Not all employees or contractors will be submitting expenses so it may=20
not be necessary to have accounts for all possible users. This is=20
something that the application owner needs to decide.

Now let's look at logistics.

Bulk load:
Each application will need an initial set of accounts set up and for=20
something like a helpdesk this could involve load 1000-100,000 accounts. =

The information needed could come from either the management server or=20
separately, say from an HR system. Many servers that I have encountered=20
limit the number of records to something like 1000, so the pagination=20
requirement is needed for this. Even when dealing with a limited subset=20
of employees or contractors you can run into this need.

Synchronization
An application that is bulk-loaded above may need to be synchronized to=20
the management server if the data did not come from the management server=
=2E

Change Management
This is really a synchronization issue as well. Changes happen all the=20
time and new employees/contractors need to be added, terminated ones=20
removed and updates happen all the time. The best way of dealing with=20
this may be to set up a message queue that each application can=20
subscribe to and they can take the needed action when it's convenient=20
for that application. It's not the only method but it's the one I found=20
to be the most helpful. There are two ways of doing that: 1. send the=20
complete user information for new accounts, send just the change for=20
updating accounts, send the ID for terminated accounts along with some=20
meta information. The other method which I have used is just to send the =

ID and whether it's new, updated or terminated.

I hope this is helpful to the discussion.

Danny



From nobody Thu Aug 19 10:33:43 2021
Return-Path: <Matt.Peterson@oneidentity.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 C664E3A0F2E for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 10:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oneidentity.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 5yzwEEUG2wfW for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 10:33:36 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2112.outbound.protection.outlook.com [40.107.243.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E97A33A0F00 for <scim@ietf.org>; Thu, 19 Aug 2021 10:33:35 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lXYJx/dgV4XQkiK1heRF21eOzOyPLaozaJr+UnAyTPeOA9rMNA8Fo+vmStaBQjXEmOGs4UZYk+C1IKYHutXNhHP5DCMA1ELdczabIe6MmTezc+Srhn/OPxVX51v08l/DY/5WSd78bYRIJCVgRymlOYOm3Xb7h7IIBI2LOIc5Sc8Ov3IketlEh4D/dgN5PkOi6oq2S2CNJTi9J3HIyDIZEuB5gE5ZW8KLi0x/TxVLBzhIg9pDRylnQv0bgMiC2+v9VYRP/9up63uVAtcvnNRp5v3BOeLIHsC4m4OdMhWq9cstArW0PCAP+oLVs3QTAHZB6dRfbg3UTbTo780vm1S2aQ==
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=r/HLx+h/YXwaoFuw6OwE9y7f9bXR89Kie1hQPBysVvs=; b=Um1kiahVb+7JoVppKyU3M7uGE6Ruakub5nUPL4kbGmXbkNuGL2/K2POKQv++etDUwHd8s7b1idUdL8rQHZP0opHWVSMxk4NmtxURPKP8KRCTINaVj7tD+PThN+Mzqz5QB2IW5ln1HVNEMv6New518MMX6jF015YOKnMKoW8AZXyA3vjT+oNrBBjd9VRb3TUIUS76jyVXXM5PLm0dJ2f1u00t5YhZtwNYh9nQrB6l8i0k8vUT3bJQTrzEpUYoQomE6GrVUSJWDx/3Gl9/cO3K679YXNIEjGt5U02GKlaKF1Z2Hu7Dyu4nPLJaZwuwk8xA48tNWK91eUVBUSoFAF8IBw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oneidentity.com; dmarc=pass action=none header.from=oneidentity.com; dkim=pass header.d=oneidentity.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oneidentity.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r/HLx+h/YXwaoFuw6OwE9y7f9bXR89Kie1hQPBysVvs=; b=Gwulrytroi0jB2OSvJ3DqbFtJ+EM9aC3U9T/m27o4nw1+a6TdEQ/CddhlAgcifAv30WBcZzSTP2bHQz7EGchd8R5UrcRKH223rO7rloOm6+aG8FGOIdT4HJzkmi5tW4jAgmss2Bcn6aBrS6zRKwBHHtdocXypshGLhMT5NZBv9B/+dqMWCx01Porm8ScTCLQgvrjdYyWvVrm3WocxHF9sExIv7IqAvTfLYCv6am+DnWdWrianb9e/HiKE0uym9KA36+a2nLeFxp3v2nwe0NeBoARSWvFm3vFfzmUdKeUrwTVVof9QARx+jhunaOvR9qUdR1XrnWna2riUxBS/a6YAQ==
Received: from MWHPR19MB0957.namprd19.prod.outlook.com (2603:10b6:300:a4::16) by MW3PR19MB4380.namprd19.prod.outlook.com (2603:10b6:303:50::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.17; Thu, 19 Aug 2021 17:33:34 +0000
Received: from MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783]) by MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783%4]) with mapi id 15.20.4415.025; Thu, 19 Aug 2021 17:33:33 +0000
From: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
To: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
Thread-Topic: [scim] SCIM Synchronization Problem
Thread-Index: AQHXlD4yOJYx7decRU+u2K9sFyDQQ6t7FibQ
Date: Thu, 19 Aug 2021 17:33:33 +0000
Message-ID: <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net>
In-Reply-To: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: pdmconsulting.net; dkim=none (message not signed) header.d=none;pdmconsulting.net; dmarc=none action=none header.from=oneidentity.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 13e664d2-e63d-41c3-9fb8-08d963377817
x-ms-traffictypediagnostic: MW3PR19MB4380:
x-microsoft-antispam-prvs: <MW3PR19MB4380D7832919BD4229C99608E1C09@MW3PR19MB4380.namprd19.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: DX9GcvnlrnoxABEDi0Y86QZRuzVM5np6NKTddbq9Hnrbwd3+Nhg9TNowXmZwPQWAoMU4hrMwonsEDDuxO0WmximUKvuudsbEKIFhkjNt0Z+a35HZfcEYfUbvwkgM+UYM4yFWmth2DH6n06WEnYnf1PiA33f35HfcMjRoAGIxGJpBoXMkFN61xUjc7xXs2hehEylg26GKGxwE3B7tpHMYf4iEOh+/d/9u4paDMK/DSIfoffml5YuFKoiOHmALyARcyTLGDYjgHzz9hWDiyn+BoBbJJoTLV+5irfKsseu8hBRDZsp/rArdkUPocyLIY8AQ014tWpo7O7tE1qDDaPieIHFTfr2JqI4Pdu68yyxla+Y85878a4301cA+8K6czIOZtPVcb0mZ+QCg+QLILcszs7+PO3ZuzMb6Djo8z791+5WsdjML4QnIskDx2ccsFg0tZYviAqUElhym/q1933iIbQcslVmrhpUPH6RB558/QFpgoKy4x2+GQj1/VFOCwj6yKeBO8D4XmhYdURyBvM0xhMRSK00C0K5n9DTdKvI1VekRKk+G/2Hn7dWx8zv+LpDZv3BrI9zDGrMBi4gHl0xgTniu9wVpD6toZ5flGNKA9WAHX5LyTKd8h2jVMLUFqXzqoxkyJr9WtVNRhJsj2Zs7F9apMRmeJkFfccXZJ2Z/Z9AM/gn0XILhCz0OGrId0nkRq21RGxyEGfF3DHKrwWoRBFV+urZ7lMe6+2xR15ztOobcP150KAMZrXC/QNXpQ/+24+nLKwhjX/fkS2xru5QqTCRcKZbeVYnMwN8ZgLY6nxg=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MWHPR19MB0957.namprd19.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(366004)(39860400002)(346002)(136003)(396003)(110136005)(45080400002)(5660300002)(52536014)(55236004)(478600001)(8936002)(8676002)(86362001)(9686003)(55016002)(122000001)(38100700002)(83380400001)(316002)(53546011)(76116006)(966005)(33656002)(186003)(66446008)(64756008)(66556008)(7696005)(66476007)(26005)(66946007)(71200400001)(6506007)(2906002)(38070700005); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?mQzYH9Z1wlt7pIroHC6K2KWZsImwi9aNqzt6fSaBWzhPfn6LAe0JOlUBRjXv?= =?us-ascii?Q?gu2f/SRjXOuhgdmoWjo8KeKHUtJPGF+RnfKsBkQPA4PWk2yyzut1fEO/ffP2?= =?us-ascii?Q?i4HsWE95jMigZzamIl1cmMzukpgAQvhfjdqRlEeCbwPRmu37ZwhaVSXk03J9?= =?us-ascii?Q?osIXl6v909A375ZbD5h0UJNEYFKVWd2YSUvIp5ScF/E1p2vwwprcS2gStELJ?= =?us-ascii?Q?XISKcwDA8hMOoi9AGXMvzf+TgKSAB2EbDIpq4GBglx0TZkY2HLvBH4U+UuE5?= =?us-ascii?Q?F0npVhwimFdn+vxmzuGksNYKmxIl/6w4VUXX9Az9LiCkvMY45qwkyh5OeKcz?= =?us-ascii?Q?eXUt6IvCg9rwc8utlg1dJEN/AUQ+S1YH3QS2j+FKPExFuoaOtuYvGq+fWtlg?= =?us-ascii?Q?+wW/MNnG2c+mZwPcdnOGYVAClR5kXFyEgAJrwWwtVWNyzFD+zmBnEfwFuuZF?= =?us-ascii?Q?XcBameWITdapTskipLu0WdNL7cTC6H/Ut5b6CqKZYSOMprmCCA8CKp28tGeb?= =?us-ascii?Q?IxPiWLYfgKdhYMAdawrWa4T049gxZNhAGoXGHSp73d0acTavGyXeVWLyDofu?= =?us-ascii?Q?b0yuy/J//sDsTvJmfGRt8VbWRSKEC1+YETOORIn6HgLElo1C3wHtBfdz9VPn?= =?us-ascii?Q?T8CrweBIyOWstWZmacZy+6jyGjUZzuWI7cFjqDxdgeTFiJ8eu/tk/ZxlOZgp?= =?us-ascii?Q?Wtz8UExq1MelQsM+BCWGisrnu2zqMrbkxaw+vftzshfG06zHUgHuqfYUX850?= =?us-ascii?Q?TlS9NPmk5Z3+ZmRQVwbFplyiO1By6vHW6tzCcS87FBku4yppfdk27794mIrp?= =?us-ascii?Q?rRix0oQzOUftL6bIKCdg2+42zjbFb51Ba1nx8QBfQQ46WGfZUmTujooYzktt?= =?us-ascii?Q?2vGF721cdiCOxTQsJ6tG+6fEclXs3u6btqb2s0Ldp1cMrX81GyX/v2OTyoZj?= =?us-ascii?Q?Z0uRWlbNp/05Mk7w1tu9UNnvbaI1aTzh7EA3qeizk9/rQD6fboRPVDsQlPpK?= =?us-ascii?Q?6QaAsyCqw3ZmKuNADK+MBJpp0YOuFXkjdromwZIrEnfDAH+0wjIOxnsHJtf4?= =?us-ascii?Q?BZsfrBIF2DcFxqWWmxfVXV+UZEYnIvUYi8xRKZyqN4PqzPZVv3wl4DMVjgOe?= =?us-ascii?Q?xdyrFYqbFIf2Sog91Wh1Jo0ZGI6u1DZ5ZiHAm3tERW6cM+curII0mjDvoRKE?= =?us-ascii?Q?AZ3QpzVec8Ldh1t/HjULt+3hL17OuWTAhF8WjCGGxczw7FI2lzKwZC5ZvUAh?= =?us-ascii?Q?3AfTa1PaGh5Bq0MnNLkz2LB4SmdB4UymG+Gg4Qb8A8+UQlPsuJ4q/W8MDvXk?= =?us-ascii?Q?s6qQNg3j0zZPBDrlVnHt+AuC?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: oneidentity.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR19MB0957.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 13e664d2-e63d-41c3-9fb8-08d963377817
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2021 17:33:33.7131 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 91c369b5-1c9e-439c-989c-1867ec606603
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: +FvVvwvPuSwy1gTQRM79/YPfOCpUKeAPgbhc3ecs7WMFsC/c4NJ6GjaObl2lihwoUtDmJpd9fPmT4jdSWd8Fhg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR19MB4380
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/cEtg22s509i8eRyZIeO_35VmXSk>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2021 17:33:42 -0000

Thank you, Danny, for creating a new thread.  The following are my comments=
 from meeting minutes (some edits):

There appears to be two use cases for "synchronization":=20

  1.  Constructing and enforcing Application authorization models -  An app=
lication (acting as a SCIM client) caches users/groups data from the IdP in=
 order to present "user/group pickers" when presenting screens used to conf=
igure the application  authorization rules (RBAC, Policy, or ACL).  Also, w=
hen the application enforces authorization, user and group data needs to be=
 immediately available so that authorization decisions can be made quickly.

  2.  Identity Management and Governance systems - implement a canonical id=
entity model" where all accounts and groups are represented.  This model is=
 used to build provisioning rules and calculate separation of duty violatio=
ns, attestations, and approvals etc.   Management-time evaluation of the mo=
del needs to be done efficiently without external calls to the SCIM service=
 provider.

Both above use cases, are "client-cache" use cases that need only a "one-wa=
y" sync (from the SCIM server to the SCIM client).   To accomplish there ar=
e two distinct steps:  a) download the initial results (users/groups) and, =
b) keep the cached copy of these initial results (user/groups) up to date w=
ith changes that are being made on the SCIM Service provider.  =20

I think it could help us narrow down the list of suitable approaches if we =
could agree that "one-way" sync (keeping a client-side cache up to date) is=
 our target.

--
Matt Peterson

-----Original Message-----
From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
Sent: Wednesday, August 18, 2021 8:34 AM
To: SCIM WG <scim@ietf.org>
Subject: [scim] SCIM Synchronization Problem

CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.


I decided that this needs it's own thread and not be part of the meeting mi=
nutes.

I have had a great deal of experience dealing with the user account synchro=
nization problem. Here's my view of the problems.

I will be calling one system Management Server and the other system Applica=
tion Server. I found client/server labels confusing. The Management Server =
is what I am defining to be the server that sends updates to add/update/rem=
ove users and groups to the Application server whose account, groups and ac=
cess permissions are being managed.

First some definitions of user accounts. There are usually more than one of=
 each of these:
1. Builtin accounts
2. Special-purpose accounts
3. Employee
4. Contractor
5. Agent
6. Customer

There may be more.

1. Builtin accounts: These are accounts that applications have and there ma=
y be more than one. There is always an admin account which can do anything,=
 for example the administrator account in Active Directory or a database ad=
min account. The application may have more accounts for other purposes.

2. Special-purpose accounts: These may be set up to provide access to other=
 applications, for example a SCIM request to a SCIM REST API should be hand=
led by a special account which cannot be used to login via a UI interface a=
nd only be able to perform certain functions. In addition there may be acco=
unts set up to listen for topics or queues on a message queue among other p=
ossibilities. Keeping separate accounts like this are important for trackin=
g in logs and applications.

3. Employee: These are accounts that employees may login to the application=
.

4. Contractors: These accounts that a contractor performing work for the co=
mpany may use to log into an application. Unlike Employee accounts these wo=
uld have an expiration date.

5. Agent: Accounts like this are for external users who may need to manage =
information for their own customers. An example of this is an insurance age=
nt logging in to handle an insurance policy for their clients.

6. Customers: These are where the customers are using the application direc=
tly. For a bank it's likely to be millions of customers. The management pla=
tform should not be involved in managing these accounts.

Let's now look at a few example applications.

1. Helpdesk
All employees and contractors will need to be able to log into a helpdesk a=
pplication and enter tickets. This means loading information about all empl=
oyees and contractors. For a company with only 1000 employees that's manage=
able. For a company with 100K employees, it's a bigger challenge.

2. Customer Support
Only employees or contractors in the department providing customer support =
need access plus a few other employees. In addition identified customers ma=
y need accounts.

3. Expenses
Not all employees or contractors will be submitting expenses so it may not =
be necessary to have accounts for all possible users. This is something tha=
t the application owner needs to decide.

Now let's look at logistics.

Bulk load:
Each application will need an initial set of accounts set up and for someth=
ing like a helpdesk this could involve load 1000-100,000 accounts.
The information needed could come from either the management server or sepa=
rately, say from an HR system. Many servers that I have encountered limit t=
he number of records to something like 1000, so the pagination requirement =
is needed for this. Even when dealing with a limited subset of employees or=
 contractors you can run into this need.

Synchronization
An application that is bulk-loaded above may need to be synchronized to the=
 management server if the data did not come from the management server.

Change Management
This is really a synchronization issue as well. Changes happen all the time=
 and new employees/contractors need to be added, terminated ones removed an=
d updates happen all the time. The best way of dealing with this may be to =
set up a message queue that each application can subscribe to and they can =
take the needed action when it's convenient for that application. It's not =
the only method but it's the one I found to be the most helpful. There are =
two ways of doing that: 1. send the complete user information for new accou=
nts, send just the change for updating accounts, send the ID for terminated=
 accounts along with some meta information. The other method which I have u=
sed is just to send the ID and whether it's new, updated or terminated.

I hope this is helpful to the discussion.

Danny


_______________________________________________
scim mailing list
scim@ietf.org
https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterson%40ques=
t.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec606603=
%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL=
CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DriJQy3jEHl=
tc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0


From nobody Thu Aug 19 10:43:03 2021
Return-Path: <Matt.Peterson@oneidentity.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 781CD3A104B for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 10:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oneidentity.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 UGzVt2DdEk20 for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 10:42:56 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2134.outbound.protection.outlook.com [40.107.244.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3C803A1042 for <scim@ietf.org>; Thu, 19 Aug 2021 10:42:55 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NWmhYqWhGtWzRyz5X64u5I58jl2yj1UzAk6CCh//W/znC0YykuUtRRUgGxfoxaQ2NRml/TKVzWe0ieOROMHXn6OHkd7vGoSR1f1HABzV7qH82ER/DUviwnA/A7RB0jvx74XA0R2WFfhjCK1YWBFTSGKG8rcQYcNQd5kLauSKIy6V1jslXQuXTHMLTJNE94zYuXOXbqu2cSokGf+todtZIrUSajp8+H3j0J0Mii/lM0bCAEgWUbGIAIteRHfnPmRkZHqbN4fDNUx8StSAHj+I2kyOdOS5k82kn8nW5pVYS5DZxZ/lR+LRqMdI/M4EO0UkV1tXYbs4uO4d5Sli8Wy1yA==
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=PMhevUSesWuc+ambTdDb9EOyHdolQ+uoVUhlbP4xxwI=; b=YdDzB76nRc4qto0JCz0UBDXSi72qjK93gH2oE6JnBdhaD4khjNLupl1XKZsti2q1GP6r3WVcc+0bgvHhXgrb0ZRG1h/lwFUDF/sQFl3bF58cRlY80OiTPFzsj+9qWZ3ZnfM6YIXRWZw7DOA21ALCjwrj8SX2qOfo3jxMPt8wsC7VO2NuUTWUiVRKBWEWIoxB6Yt5KNaWLTsAtJ6lDIwwPQyCVMQlsTvcMUkC/C8WSl4PlDYzzKGpYDeXlhNhPHtrd7HbIcholspF0dnDhkuhBvtuBQLGkwp6876wBHWsO70O+2+bjHEy5qg92KmUxyaMX2mx/SB4yVWjThDPh3EA/w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oneidentity.com; dmarc=pass action=none header.from=oneidentity.com; dkim=pass header.d=oneidentity.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oneidentity.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PMhevUSesWuc+ambTdDb9EOyHdolQ+uoVUhlbP4xxwI=; b=iBb0PYpYSiJ+BZsMeNnG5G/GSOL5BtlfXi3TmqjQPw+pRnFm813Gy/ELxJTrERQURqloI7N08RjQaI5wTkBJd+/MuyBN4PGAXHUWKEJHNUjOPa+lRNutG6j3BUzHTGvsNEwJsR5lhyhdi4uoqh7BxjzVjBTXXehcrxt82XakXeQN9EvlCbO6geq/09zXIynRqZYDx3sx3hJkPckURO3AlnM4lpquAxoW35efERjDyohyNAFz68WAstWotMeR26zVwo/fhYFOX5JI9QwLfJCk5kCAJrGsGdgnfRFYfQU/eD1oxK6EAE85OrXf63wQSuKN1ZlPBa1NDoUCJxXX28Q4hQ==
Received: from MWHPR19MB0957.namprd19.prod.outlook.com (2603:10b6:300:a4::16) by MWHPR19MB1087.namprd19.prod.outlook.com (2603:10b6:300:a2::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19; Thu, 19 Aug 2021 17:42:54 +0000
Received: from MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783]) by MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783%4]) with mapi id 15.20.4415.025; Thu, 19 Aug 2021 17:42:54 +0000
From: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
To: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
Thread-Topic: [scim] SCIM Synchronization Problem
Thread-Index: AQHXlD4yOJYx7decRU+u2K9sFyDQQ6t7GC/Q
Date: Thu, 19 Aug 2021 17:42:53 +0000
Message-ID: <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net>
In-Reply-To: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: pdmconsulting.net; dkim=none (message not signed) header.d=none;pdmconsulting.net; dmarc=none action=none header.from=oneidentity.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3cf9f26b-0eee-4d0b-c455-08d96338c60e
x-ms-traffictypediagnostic: MWHPR19MB1087:
x-microsoft-antispam-prvs: <MWHPR19MB10870332DB8F8C6EBC2D59D6E1C09@MWHPR19MB1087.namprd19.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: LTtGm3ez5qXukLpInUbVnOI7jmMqnQXuzj2FRkWpVsixwu5AyziwfyjQgbreN/HEP7okdZUq7QVND2JILsrROtGv940DY7hgN2TmdTc4mZNqKnbhFXGVstXU6ZmDrPQtULGFz+kaz5FbJqnkkzk2JdzVHmfoPqoYxBn+2F1GIq5k4lumdtdMzEecO9n8ouoviosZepjrS1cTqG/pri/RDZOhAMBfzh4wDq0u8drFyQBVWBt1k7I/reoQeiVHuU4CZyn4to24KLwULDAa3YMXvlLBSf9ZyF8KdM+gTx6uc/JZX7LQ4bLdmRS2RNg8iOcLhwn20UE46CbY+sSu01askx2ULbJYV3fEfv2vk3FOZxixh32mtkFqUbjpRS108BXmBgDCm7gnIIhDuDzBlm3EXHzLIdIsfpiTNntd/tgE6AC9HhMzbP/ftb8q5IRxPGlu0ryBCWmJ4gA1JIq2cA//qIeY4OyBI2bvcAj5PdbBpaeKbiss2JPx9Ln61fbf+iODnbtphdoqntG627wh2BKN9L94jiyCnOkmjsXXYGtU24jSPd9abGgGN60GRNlbDcU/eo0y/7AUh1Lddow8pv2K13r/11M2ZuNkyBc7P6h3U2AsJYNsDwoYMwx3acHvHUANOllbk1koRTgtSWoLYn75GgMDiv6w6pGHj4xp5ZdLAPzifWjiuRkWfmLcIfDbHPDLbbLlw08qwXosgXEBeVdt0/pwnrAx0lQ4v5KyLaHCWY/WzMh/xFRWmLS2E1X1gvYIiukQOY0MRg2RikJfEnG81k9CFQoywZclbjG/8s93DF0=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MWHPR19MB0957.namprd19.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(366004)(396003)(39850400004)(136003)(376002)(33656002)(478600001)(53546011)(6506007)(45080400002)(110136005)(7696005)(316002)(122000001)(38100700002)(38070700005)(66556008)(66476007)(76116006)(8936002)(64756008)(71200400001)(66446008)(9686003)(66946007)(52536014)(5660300002)(2906002)(83380400001)(55236004)(966005)(8676002)(55016002)(26005)(186003)(86362001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?8rYoExd7GE3fLCaYiAh9abd+1rmpZjR5peqwcUNCdxwuL9+1SOZ6zr0UiULb?= =?us-ascii?Q?cxHRVOKJ68z48yd46G/C7U/RVugeeezo3NeQ3i+GGtbe15BwSSdjZIp9GMBm?= =?us-ascii?Q?32f2OivsL5l5nU2lTAZtsVN9UJUfDiDLaJxOlc91SCKKFDyJ5J31mf2aj28m?= =?us-ascii?Q?Drrc7iNe6c38z1dyaz4TCy9gQOoMhG6Xnv9GYmLO/Z2uEHhQmmZ4bn7/Q5WM?= =?us-ascii?Q?Iue/IizYLKdNS/myfDDwfqeH2pFQT1r565C9YVPikzdPJqVp6sooVxqGp4Ik?= =?us-ascii?Q?ammy+1C1qEaha/xgG/RoHAFMuIJ2f8cx0fAEYTGz0XB+RJqXfIM2cluiokpI?= =?us-ascii?Q?6IUV3Pzack+il4jhQ0GTSsgXnZH8ArfLU1q/z23Uy+AEq9OGiRggMtay0YH3?= =?us-ascii?Q?E0uMof6Tm/84glRmBkYKQwUf19flB7Oxslifj2agyxftTLhJbeqEPZN6bWAE?= =?us-ascii?Q?bLHe9J3VQUBd1WmMJ00W2ie9Cq9JxNZ61q90YHqUuy3QKDUS50bwO/YWyF/W?= =?us-ascii?Q?JU+czH9Cc+L4pfgiiPMn0o6xLdsi/PcT8re9LOud4rOdwiq0njLU7R72sf97?= =?us-ascii?Q?cLB5SOoYmP12TCxGXG9+rgHM+x1O/qgM+bUhyF6/SWUbBtqwfdhc3NAmv3XH?= =?us-ascii?Q?lxnmGMio/67oDHjsTP58xLzRVWxcMMpMQesef1vAz7a5UNkTI5HmgE+aFV5Z?= =?us-ascii?Q?hbRNlQS9PGhTTisZigutz0s9SqNQBob+ZAdZJFHaJ/2d3kc3tHziMO14RbVr?= =?us-ascii?Q?CzGibXYQ8QJDcxnAvcqsipc4/aC9u0EpOd5KRBygwvbkx9uK3YEVU962VKFM?= =?us-ascii?Q?qU0HXVtcRhzEt85JwEHLG0b3CfpfZmhAnLg5HmdHajflrKhFVJ70d95JB0p3?= =?us-ascii?Q?SasP4/juopqwP5xmkPmMLlliUDihrVLa+hY4SYijkxY5a0mpawbUQ4emfc0r?= =?us-ascii?Q?A1NbA19H0yDkrtkkt6oc1vj9xieThOr/53PKyDoKiuQsKW20QEX32Er7TKyf?= =?us-ascii?Q?s7Z94er8QfdkopcwKb2/vgxqLAQJkqr1xTfnvt9x0snPQhLP62R7mcTQY9pv?= =?us-ascii?Q?PnZq2T4ZD24cQuw3LD6Qj7sI1Ceb8xzKSMsjetMFmwpPy4LX2fWXHpZAZLj+?= =?us-ascii?Q?gF9qSVc1cnVir7kQPJ/chD82ACdS51+edUB2RS2ZkY0+ApjoAV1fnQIuxdNb?= =?us-ascii?Q?4xZC8Ff3dz51A2FnQNHZGbrooTC+XWeNnOVLn9X2YsXXZ9wNJVtz1/AMUEfK?= =?us-ascii?Q?uehJmfTl8VGM/1C6ypiPbNOcjUp8dprnoFxj3oGlrjxhUJ0dPGZ6Pg2MzcR3?= =?us-ascii?Q?m7BY6s2S7NYYCQPb6VYE05Dl?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: oneidentity.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR19MB0957.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3cf9f26b-0eee-4d0b-c455-08d96338c60e
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Aug 2021 17:42:54.0351 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 91c369b5-1c9e-439c-989c-1867ec606603
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tahaYRqyWVAlnQothYXPixh7Boy5gIkfPWbUEP5bbcJO5asfD1PI4RgP8TANDBrrUYamo4yqYwuOxzHmjlw1ng==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR19MB1087
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/jm7jR98cZh3wliOme1quZu4VDwE>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2021 17:43:02 -0000

Danny,

To help me understand in your post is the "SCIM Client" and what is the "SC=
IM Server" can you tell me which of your components (the Management Server =
or the Application Server) implements SCIM endpoints?  =20

The component that acts as a "SCIM Server" is the component that provides t=
he of WebAPI endpoints that conform to the SCIM spec.  For example, the  /u=
ser, /group SCIM endpoints.=20

The component(s) that uses these endpoints to query (GET)  users/groups or =
to create (POST) user/groups is the "SCIM client".

--
Matt=20

-----Original Message-----
From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
Sent: Wednesday, August 18, 2021 8:34 AM
To: SCIM WG <scim@ietf.org>
Subject: [scim] SCIM Synchronization Problem

CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.


I decided that this needs it's own thread and not be part of the meeting mi=
nutes.

I have had a great deal of experience dealing with the user account synchro=
nization problem. Here's my view of the problems.

I will be calling one system Management Server and the other system Applica=
tion Server. I found client/server labels confusing. The Management Server =
is what I am defining to be the server that sends updates to add/update/rem=
ove users and groups to the Application server whose account, groups and ac=
cess permissions are being managed.

First some definitions of user accounts. There are usually more than one of=
 each of these:
1. Builtin accounts
2. Special-purpose accounts
3. Employee
4. Contractor
5. Agent
6. Customer

There may be more.

1. Builtin accounts: These are accounts that applications have and there ma=
y be more than one. There is always an admin account which can do anything,=
 for example the administrator account in Active Directory or a database ad=
min account. The application may have more accounts for other purposes.

2. Special-purpose accounts: These may be set up to provide access to other=
 applications, for example a SCIM request to a SCIM REST API should be hand=
led by a special account which cannot be used to login via a UI interface a=
nd only be able to perform certain functions. In addition there may be acco=
unts set up to listen for topics or queues on a message queue among other p=
ossibilities. Keeping separate accounts like this are important for trackin=
g in logs and applications.

3. Employee: These are accounts that employees may login to the application=
.

4. Contractors: These accounts that a contractor performing work for the co=
mpany may use to log into an application. Unlike Employee accounts these wo=
uld have an expiration date.

5. Agent: Accounts like this are for external users who may need to manage =
information for their own customers. An example of this is an insurance age=
nt logging in to handle an insurance policy for their clients.

6. Customers: These are where the customers are using the application direc=
tly. For a bank it's likely to be millions of customers. The management pla=
tform should not be involved in managing these accounts.

Let's now look at a few example applications.

1. Helpdesk
All employees and contractors will need to be able to log into a helpdesk a=
pplication and enter tickets. This means loading information about all empl=
oyees and contractors. For a company with only 1000 employees that's manage=
able. For a company with 100K employees, it's a bigger challenge.

2. Customer Support
Only employees or contractors in the department providing customer support =
need access plus a few other employees. In addition identified customers ma=
y need accounts.

3. Expenses
Not all employees or contractors will be submitting expenses so it may not =
be necessary to have accounts for all possible users. This is something tha=
t the application owner needs to decide.

Now let's look at logistics.

Bulk load:
Each application will need an initial set of accounts set up and for someth=
ing like a helpdesk this could involve load 1000-100,000 accounts.
The information needed could come from either the management server or sepa=
rately, say from an HR system. Many servers that I have encountered limit t=
he number of records to something like 1000, so the pagination requirement =
is needed for this. Even when dealing with a limited subset of employees or=
 contractors you can run into this need.

Synchronization
An application that is bulk-loaded above may need to be synchronized to the=
 management server if the data did not come from the management server.

Change Management
This is really a synchronization issue as well. Changes happen all the time=
 and new employees/contractors need to be added, terminated ones removed an=
d updates happen all the time. The best way of dealing with this may be to =
set up a message queue that each application can subscribe to and they can =
take the needed action when it's convenient for that application. It's not =
the only method but it's the one I found to be the most helpful. There are =
two ways of doing that: 1. send the complete user information for new accou=
nts, send just the change for updating accounts, send the ID for terminated=
 accounts along with some meta information. The other method which I have u=
sed is just to send the ID and whether it's new, updated or terminated.

I hope this is helpful to the discussion.

Danny


_______________________________________________
scim mailing list
scim@ietf.org
https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterson%40ques=
t.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec606603=
%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL=
CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DriJQy3jEHl=
tc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0


From nobody Thu Aug 19 11:05:57 2021
Return-Path: <phil.hunt@independentid.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 A26C23A1288 for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 11:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 y1lDQlfWGAj5 for <scim@ietfa.amsl.com>; Thu, 19 Aug 2021 11:05:48 -0700 (PDT)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 8185E3A1287 for <scim@ietf.org>; Thu, 19 Aug 2021 11:05:48 -0700 (PDT)
Received: by mail-pf1-x42c.google.com with SMTP id g14so6237876pfm.1 for <scim@ietf.org>; Thu, 19 Aug 2021 11:05:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=xH5rJizyXGxOzeZWtGSITBQEJg6ZBiir8mVHvAlRd2c=; b=NbKInv9bnmVjF4Kq/yyPx0Y9pnsr9knFNEM+6BzZ3JcjTTxmr8pbQGHtVodQYvTmZv fgQuDBLNroS3Kd9fztFSSmnH6gCOOzPlzNWNQO0+VRoI4LtEWe0+ITGlxPM/qxga3I+o XZmyvJwwzEY5imOsNfjuN6VEMDdYNTbJRMvOrvXBeZlSA3MBTR8/RKE9AOPqaom4wVyM Ve9SVI5sNxM0Nc9dRK+Khpk6tR8y8fpEall7sdX2mgRro065dAkUYmHuXWivtCj9R1Uy GCfqCNDXOQGNkvM2K+lEHE5Hip/XYWVK7wdkt6/iid+zJNNRO/+zAkMxtBrr9bEo5qyY lWKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=xH5rJizyXGxOzeZWtGSITBQEJg6ZBiir8mVHvAlRd2c=; b=JBuzvir1Tsyv3rMWf0b5oSAXXbyYDLDOAGO8Lp4ZvJr7t+3ll/Pra2VMxtF5TzYCjr iaZZbYN4mfdCICeS/HksxovVH1KeXW7QDbT2tsILZEl3EwcbvN7sM2qO7a84LweELiIU FAaneQjtIlRHAvSui/LLJA0k0DGX5k6P86522hd0CusfU642C6OjzvdsHuhZnJwiEFNO HtXQbbnysaaexn0dyEmmysTqcMh3lsfczVbuDPupNZC+IVVCGu3Lb5szDV5WIUjUKerZ v6woAzbGeV1qtHWkbYFp39y9aj8hF5uC+k/RrkwCZlX49isD04jdOYLoyTeg0szcsEnp s/JQ==
X-Gm-Message-State: AOAM532kKDzMXAyf+RoYaoirW+FCuS470ukH8CC2cSWCyguXYnlLZ8MK bXpjZH2fnUkDIpoDkpGvj1e48fE2jiEIew==
X-Google-Smtp-Source: ABdhPJwDbAKnWgFW/t8xCeBG0Cdz4pSXP6sJGcarByvahNguDi3vzeTsmomCn/zdNrN2qv96a0/O9w==
X-Received: by 2002:a63:214c:: with SMTP id s12mr15194846pgm.86.1629396346624;  Thu, 19 Aug 2021 11:05:46 -0700 (PDT)
Received: from smtpclient.apple ([2605:8d80:460:eba7:c9be:1b67:3ecb:7a12]) by smtp.gmail.com with ESMTPSA id r3sm4013111pff.119.2021.08.19.11.05.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Aug 2021 11:05:46 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 19 Aug 2021 11:05:43 -0700
Message-Id: <11DC0D05-6988-46BE-93B0-80F1244A3779@independentid.com>
References: <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
Cc: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
In-Reply-To: <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
To: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (18G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/NVAzTm3Bt6mTIJtIlCyWul3GBcs>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Aug 2021 18:05:55 -0000

This is good high level case information.=20

Matt, you make a good case for access control standards. It brings out some q=
uestions=E2=80=A6

Is syncing users and groups enough or must access policy rules/data be synch=
ronized (assuming a common standard for policy)?  How close must separate do=
mains be to work this well together? Is it true that access control is the s=
ame across domains?

These issues are what led me to believe client/server RESTful =E2=80=9Ccomma=
nd=E2=80=9Ds like POST/PUT/PATCH are insufficient. Instead, what if an event=
 in one domain is published and a subscriber decides how to process the even=
t? In command mode the requestor has to know the command will work. In event=
 mode, the receiver has context to interpret and translate into local comman=
ds.=20

Maybe we can do a con call and go through security events and how they suppo=
rt arms length cross domain relationships.=20

Phil

> On Aug 19, 2021, at 10:33 AM, Matt Peterson (mpeterso) <Matt.Peterson=3D40=
oneidentity.com@dmarc.ietf.org> wrote:
>=20
> =EF=BB=BFThank you, Danny, for creating a new thread.  The following are m=
y comments from meeting minutes (some edits):
>=20
> There appears to be two use cases for "synchronization":=20
>=20
>  1.  Constructing and enforcing Application authorization models -  An app=
lication (acting as a SCIM client) caches users/groups data from the IdP in o=
rder to present "user/group pickers" when presenting screens used to configu=
re the application  authorization rules (RBAC, Policy, or ACL).  Also, when t=
he application enforces authorization, user and group data needs to be immed=
iately available so that authorization decisions can be made quickly.
>=20
>  2.  Identity Management and Governance systems - implement a canonical id=
entity model" where all accounts and groups are represented.  This model is u=
sed to build provisioning rules and calculate separation of duty violations,=
 attestations, and approvals etc.   Management-time evaluation of the model n=
eeds to be done efficiently without external calls to the SCIM service provi=
der.
>=20
> Both above use cases, are "client-cache" use cases that need only a "one-w=
ay" sync (from the SCIM server to the SCIM client).   To accomplish there ar=
e two distinct steps:  a) download the initial results (users/groups) and, b=
) keep the cached copy of these initial results (user/groups) up to date wit=
h changes that are being made on the SCIM Service provider.  =20
>=20
> I think it could help us narrow down the list of suitable approaches if we=
 could agree that "one-way" sync (keeping a client-side cache up to date) is=
 our target.
>=20
> --
> Matt Peterson
>=20
> -----Original Message-----
> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> Sent: Wednesday, August 18, 2021 8:34 AM
> To: SCIM WG <scim@ietf.org>
> Subject: [scim] SCIM Synchronization Problem
>=20
> CAUTION: This email originated from outside of the organization. Do not fo=
llow guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.
>=20
>=20
> I decided that this needs it's own thread and not be part of the meeting m=
inutes.
>=20
> I have had a great deal of experience dealing with the user account synchr=
onization problem. Here's my view of the problems.
>=20
> I will be calling one system Management Server and the other system Applic=
ation Server. I found client/server labels confusing. The Management Server i=
s what I am defining to be the server that sends updates to add/update/remov=
e users and groups to the Application server whose account, groups and acces=
s permissions are being managed.
>=20
> First some definitions of user accounts. There are usually more than one o=
f each of these:
> 1. Builtin accounts
> 2. Special-purpose accounts
> 3. Employee
> 4. Contractor
> 5. Agent
> 6. Customer
>=20
> There may be more.
>=20
> 1. Builtin accounts: These are accounts that applications have and there m=
ay be more than one. There is always an admin account which can do anything,=
 for example the administrator account in Active Directory or a database adm=
in account. The application may have more accounts for other purposes.
>=20
> 2. Special-purpose accounts: These may be set up to provide access to othe=
r applications, for example a SCIM request to a SCIM REST API should be hand=
led by a special account which cannot be used to login via a UI interface an=
d only be able to perform certain functions. In addition there may be accoun=
ts set up to listen for topics or queues on a message queue among other poss=
ibilities. Keeping separate accounts like this are important for tracking in=
 logs and applications.
>=20
> 3. Employee: These are accounts that employees may login to the applicatio=
n.
>=20
> 4. Contractors: These accounts that a contractor performing work for the c=
ompany may use to log into an application. Unlike Employee accounts these wo=
uld have an expiration date.
>=20
> 5. Agent: Accounts like this are for external users who may need to manage=
 information for their own customers. An example of this is an insurance age=
nt logging in to handle an insurance policy for their clients.
>=20
> 6. Customers: These are where the customers are using the application dire=
ctly. For a bank it's likely to be millions of customers. The management pla=
tform should not be involved in managing these accounts.
>=20
> Let's now look at a few example applications.
>=20
> 1. Helpdesk
> All employees and contractors will need to be able to log into a helpdesk a=
pplication and enter tickets. This means loading information about all emplo=
yees and contractors. For a company with only 1000 employees that's manageab=
le. For a company with 100K employees, it's a bigger challenge.
>=20
> 2. Customer Support
> Only employees or contractors in the department providing customer support=
 need access plus a few other employees. In addition identified customers ma=
y need accounts.
>=20
> 3. Expenses
> Not all employees or contractors will be submitting expenses so it may not=
 be necessary to have accounts for all possible users. This is something tha=
t the application owner needs to decide.
>=20
> Now let's look at logistics.
>=20
> Bulk load:
> Each application will need an initial set of accounts set up and for somet=
hing like a helpdesk this could involve load 1000-100,000 accounts.
> The information needed could come from either the management server or sep=
arately, say from an HR system. Many servers that I have encountered limit t=
he number of records to something like 1000, so the pagination requirement i=
s needed for this. Even when dealing with a limited subset of employees or c=
ontractors you can run into this need.
>=20
> Synchronization
> An application that is bulk-loaded above may need to be synchronized to th=
e management server if the data did not come from the management server.
>=20
> Change Management
> This is really a synchronization issue as well. Changes happen all the tim=
e and new employees/contractors need to be added, terminated ones removed an=
d updates happen all the time. The best way of dealing with this may be to s=
et up a message queue that each application can subscribe to and they can ta=
ke the needed action when it's convenient for that application. It's not the=
 only method but it's the one I found to be the most helpful. There are two w=
ays of doing that: 1. send the complete user information for new accounts, s=
end just the change for updating accounts, send the ID for terminated accoun=
ts along with some meta information. The other method which I have used is j=
ust to send the ID and whether it's new, updated or terminated.
>=20
> I hope this is helpful to the discussion.
>=20
> Danny
>=20
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.ie=
tf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterson%40ques=
t.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec606603%=
7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ=
QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DriJQy3jEHltc6=
ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim


From nobody Fri Aug 20 07:46:33 2021
Return-Path: <mayer@pdmconsulting.net>
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 9FA503A0C38 for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 07:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 J0Yhu3RqxY-r for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 07:46:25 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6411B3A0C40 for <scim@ietf.org>; Fri, 20 Aug 2021 07:46:20 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GrkwT0cDszMNWd; Fri, 20 Aug 2021 14:46:16 +0000 (UTC)
To: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>, SCIM WG <scim@ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <0f21255e-4ea9-b42d-353d-5c0661e1be5e@pdmconsulting.net>
Date: Fri, 20 Aug 2021 10:46:15 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/5uj2n0sU4URXPodxVh5Udsh2nw4>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 14:46:32 -0000

It's not that simple. If an administrator goes in an adds a new account 
or updates an existing account and adds permissions to it, how will the 
management side know? The way I did it was to have the application 
monitor for those changes and notify the management server of the 
changes. I did this via a message queue for our internal applications. 
The management server needs to decide how to handle these violations.

Danny

On 8/19/21 1:33 PM, Matt Peterson (mpeterso) wrote:
> Thank you, Danny, for creating a new thread.  The following are my comments from meeting minutes (some edits):
>
> There appears to be two use cases for "synchronization":
>
>    1.  Constructing and enforcing Application authorization models -  An application (acting as a SCIM client) caches users/groups data from the IdP in order to present "user/group pickers" when presenting screens used to configure the application  authorization rules (RBAC, Policy, or ACL).  Also, when the application enforces authorization, user and group data needs to be immediately available so that authorization decisions can be made quickly.
>
>    2.  Identity Management and Governance systems - implement a canonical identity model" where all accounts and groups are represented.  This model is used to build provisioning rules and calculate separation of duty violations, attestations, and approvals etc.   Management-time evaluation of the model needs to be done efficiently without external calls to the SCIM service provider.
>
> Both above use cases, are "client-cache" use cases that need only a "one-way" sync (from the SCIM server to the SCIM client).   To accomplish there are two distinct steps:  a) download the initial results (users/groups) and, b) keep the cached copy of these initial results (user/groups) up to date with changes that are being made on the SCIM Service provider.
>
> I think it could help us narrow down the list of suitable approaches if we could agree that "one-way" sync (keeping a client-side cache up to date) is our target.
>
> --
> Matt Peterson
>
> -----Original Message-----
> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> Sent: Wednesday, August 18, 2021 8:34 AM
> To: SCIM WG <scim@ietf.org>
> Subject: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>
>
> I decided that this needs it's own thread and not be part of the meeting minutes.
>
> I have had a great deal of experience dealing with the user account synchronization problem. Here's my view of the problems.
>
> I will be calling one system Management Server and the other system Application Server. I found client/server labels confusing. The Management Server is what I am defining to be the server that sends updates to add/update/remove users and groups to the Application server whose account, groups and access permissions are being managed.
>
> First some definitions of user accounts. There are usually more than one of each of these:
> 1. Builtin accounts
> 2. Special-purpose accounts
> 3. Employee
> 4. Contractor
> 5. Agent
> 6. Customer
>
> There may be more.
>
> 1. Builtin accounts: These are accounts that applications have and there may be more than one. There is always an admin account which can do anything, for example the administrator account in Active Directory or a database admin account. The application may have more accounts for other purposes.
>
> 2. Special-purpose accounts: These may be set up to provide access to other applications, for example a SCIM request to a SCIM REST API should be handled by a special account which cannot be used to login via a UI interface and only be able to perform certain functions. In addition there may be accounts set up to listen for topics or queues on a message queue among other possibilities. Keeping separate accounts like this are important for tracking in logs and applications.
>
> 3. Employee: These are accounts that employees may login to the application.
>
> 4. Contractors: These accounts that a contractor performing work for the company may use to log into an application. Unlike Employee accounts these would have an expiration date.
>
> 5. Agent: Accounts like this are for external users who may need to manage information for their own customers. An example of this is an insurance agent logging in to handle an insurance policy for their clients.
>
> 6. Customers: These are where the customers are using the application directly. For a bank it's likely to be millions of customers. The management platform should not be involved in managing these accounts.
>
> Let's now look at a few example applications.
>
> 1. Helpdesk
> All employees and contractors will need to be able to log into a helpdesk application and enter tickets. This means loading information about all employees and contractors. For a company with only 1000 employees that's manageable. For a company with 100K employees, it's a bigger challenge.
>
> 2. Customer Support
> Only employees or contractors in the department providing customer support need access plus a few other employees. In addition identified customers may need accounts.
>
> 3. Expenses
> Not all employees or contractors will be submitting expenses so it may not be necessary to have accounts for all possible users. This is something that the application owner needs to decide.
>
> Now let's look at logistics.
>
> Bulk load:
> Each application will need an initial set of accounts set up and for something like a helpdesk this could involve load 1000-100,000 accounts.
> The information needed could come from either the management server or separately, say from an HR system. Many servers that I have encountered limit the number of records to something like 1000, so the pagination requirement is needed for this. Even when dealing with a limited subset of employees or contractors you can run into this need.
>
> Synchronization
> An application that is bulk-loaded above may need to be synchronized to the management server if the data did not come from the management server.
>
> Change Management
> This is really a synchronization issue as well. Changes happen all the time and new employees/contractors need to be added, terminated ones removed and updates happen all the time. The best way of dealing with this may be to set up a message queue that each application can subscribe to and they can take the needed action when it's convenient for that application. It's not the only method but it's the one I found to be the most helpful. There are two ways of doing that: 1. send the complete user information for new accounts, send just the change for updating accounts, send the ID for terminated accounts along with some meta information. The other method which I have used is just to send the ID and whether it's new, updated or terminated.
>
> I hope this is helpful to the discussion.
>
> Danny
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7Cmatt.peterson%40quest.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=riJQy3jEHltc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=0
>


From nobody Fri Aug 20 07:54:30 2021
Return-Path: <mayer@pdmconsulting.net>
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 7FE6A3A0D3B for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 07:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ih9H27Og5djf for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 07:54:23 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D94A3A0D36 for <scim@ietf.org>; Fri, 20 Aug 2021 07:54:21 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4Grl5l2DwyzMNWd; Fri, 20 Aug 2021 14:54:19 +0000 (UTC)
To: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>, SCIM WG <scim@ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net>
Date: Fri, 20 Aug 2021 10:54:18 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/1s8ATT3HFwSBRmKhJZ7QGICrQ3o>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 14:54:29 -0000

I decided to avoid the client/server naming convention because I find it =

confusing. The system responsible for managing the user accounts and=20
groups I have declared to be the Management server. I believe you=20
describe this as the "SCIM Client" and is used to GET/POST/PATCH, etc.=20
to the Application server to maintain the user accounts and groups. The=20
application server is what I believe you call the "SCIM Server". This=20
provides the SCIM API's needed.

I find the use of client/server not helpful to understand their role in=20
the protocol.

Danny

On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
> Danny,
>
> To help me understand in your post is the "SCIM Client" and what is the=
 "SCIM Server" can you tell me which of your components (the Management S=
erver or the Application Server) implements SCIM endpoints?
>
> The component that acts as a "SCIM Server" is the component that provid=
es the of WebAPI endpoints that conform to the SCIM spec.  For example, t=
he  /user, /group SCIM endpoints.
>
> The component(s) that uses these endpoints to query (GET)  users/groups=
 or to create (POST) user/groups is the "SCIM client".
>
> --
> Matt
>
> -----Original Message-----
> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> Sent: Wednesday, August 18, 2021 8:34 AM
> To: SCIM WG <scim@ietf.org>
> Subject: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not=
 follow guidance, click links, or open attachments unless you recognize t=
he sender and know the content is safe.
>
>
> I decided that this needs it's own thread and not be part of the meetin=
g minutes.
>
> I have had a great deal of experience dealing with the user account syn=
chronization problem. Here's my view of the problems.
>
> I will be calling one system Management Server and the other system App=
lication Server. I found client/server labels confusing. The Management S=
erver is what I am defining to be the server that sends updates to add/up=
date/remove users and groups to the Application server whose account, gro=
ups and access permissions are being managed.
>
> First some definitions of user accounts. There are usually more than on=
e of each of these:
> 1. Builtin accounts
> 2. Special-purpose accounts
> 3. Employee
> 4. Contractor
> 5. Agent
> 6. Customer
>
> There may be more.
>
> 1. Builtin accounts: These are accounts that applications have and ther=
e may be more than one. There is always an admin account which can do any=
thing, for example the administrator account in Active Directory or a dat=
abase admin account. The application may have more accounts for other pur=
poses.
>
> 2. Special-purpose accounts: These may be set up to provide access to o=
ther applications, for example a SCIM request to a SCIM REST API should b=
e handled by a special account which cannot be used to login via a UI int=
erface and only be able to perform certain functions. In addition there m=
ay be accounts set up to listen for topics or queues on a message queue a=
mong other possibilities. Keeping separate accounts like this are importa=
nt for tracking in logs and applications.
>
> 3. Employee: These are accounts that employees may login to the applica=
tion.
>
> 4. Contractors: These accounts that a contractor performing work for th=
e company may use to log into an application. Unlike Employee accounts th=
ese would have an expiration date.
>
> 5. Agent: Accounts like this are for external users who may need to man=
age information for their own customers. An example of this is an insuran=
ce agent logging in to handle an insurance policy for their clients.
>
> 6. Customers: These are where the customers are using the application d=
irectly. For a bank it's likely to be millions of customers. The manageme=
nt platform should not be involved in managing these accounts.
>
> Let's now look at a few example applications.
>
> 1. Helpdesk
> All employees and contractors will need to be able to log into a helpde=
sk application and enter tickets. This means loading information about al=
l employees and contractors. For a company with only 1000 employees that'=
s manageable. For a company with 100K employees, it's a bigger challenge.=

>
> 2. Customer Support
> Only employees or contractors in the department providing customer supp=
ort need access plus a few other employees. In addition identified custom=
ers may need accounts.
>
> 3. Expenses
> Not all employees or contractors will be submitting expenses so it may =
not be necessary to have accounts for all possible users. This is somethi=
ng that the application owner needs to decide.
>
> Now let's look at logistics.
>
> Bulk load:
> Each application will need an initial set of accounts set up and for so=
mething like a helpdesk this could involve load 1000-100,000 accounts.
> The information needed could come from either the management server or =
separately, say from an HR system. Many servers that I have encountered l=
imit the number of records to something like 1000, so the pagination requ=
irement is needed for this. Even when dealing with a limited subset of em=
ployees or contractors you can run into this need.
>
> Synchronization
> An application that is bulk-loaded above may need to be synchronized to=
 the management server if the data did not come from the management serve=
r.
>
> Change Management
> This is really a synchronization issue as well. Changes happen all the =
time and new employees/contractors need to be added, terminated ones remo=
ved and updates happen all the time. The best way of dealing with this ma=
y be to set up a message queue that each application can subscribe to and=
 they can take the needed action when it's convenient for that applicatio=
n. It's not the only method but it's the one I found to be the most helpf=
ul. There are two ways of doing that: 1. send the complete user informati=
on for new accounts, send just the change for updating accounts, send the=
 ID for terminated accounts along with some meta information. The other m=
ethod which I have used is just to send the ID and whether it's new, upda=
ted or terminated.
>
> I hope this is helpful to the discussion.
>
> Danny
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
=2Eietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterso=
n%40quest.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c18=
67ec606603%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM=
C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdat=
a=3DriJQy3jEHltc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0
>


From nobody Fri Aug 20 08:05:02 2021
Return-Path: <mayer@pdmconsulting.net>
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 2CD0D3A0E39 for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 08:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 sXO_iN6LAvXN for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 08:04:54 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ACF63A0E2A for <scim@ietf.org>; Fri, 20 Aug 2021 08:04:54 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GrlKt6fFmzMNWd; Fri, 20 Aug 2021 15:04:50 +0000 (UTC)
To: Phillip Hunt <phil.hunt@independentid.com>, "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
Cc: SCIM WG <scim@ietf.org>
References: <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <11DC0D05-6988-46BE-93B0-80F1244A3779@independentid.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net>
Date: Fri, 20 Aug 2021 11:04:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <11DC0D05-6988-46BE-93B0-80F1244A3779@independentid.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/1NFjmUXz44ZzfxrexCkdroLtUyc>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 15:05:00 -0000

You cannot assume that the groups are the same across different=20
application domains. In our case each group was totally different and=20
had different permissions associated with it. In addition you can have=20
different permissions associated individually to a user account.=20
Microsoft's NTFS access controls are a good example of this.

The SCIM Config information should include information on what commands=20
are available on that system. In addition the application needs to=20
notify the requestor that if something went wrong why it went wrong. For =

example, in my cases if a request for a group to be added to a user=20
cannot be fulfilled because the group does not exist then the failure=20
needs to be reported back. Also for our builtin and special accounts,=20
the requestor cannot make any changes.

Does this help?

Danny

On 8/19/21 2:05 PM, Phillip Hunt wrote:
> This is good high level case information.
>
> Matt, you make a good case for access control standards. It brings out =
some questions=E2=80=A6
>
> Is syncing users and groups enough or must access policy rules/data be =
synchronized (assuming a common standard for policy)?  How close must sep=
arate domains be to work this well together? Is it true that access contr=
ol is the same across domains?
>
> These issues are what led me to believe client/server RESTful =E2=80=9C=
command=E2=80=9Ds like POST/PUT/PATCH are insufficient. Instead, what if =
an event in one domain is published and a subscriber decides how to proce=
ss the event? In command mode the requestor has to know the command will =
work. In event mode, the receiver has context to interpret and translate =
into local commands.
>
> Maybe we can do a con call and go through security events and how they =
support arms length cross domain relationships.
>
> Phil
>
>> On Aug 19, 2021, at 10:33 AM, Matt Peterson (mpeterso) <Matt.Peterson=3D=
40oneidentity.com@dmarc.ietf.org> wrote:
>>
>> =EF=BB=BFThank you, Danny, for creating a new thread.  The following a=
re my comments from meeting minutes (some edits):
>>
>> There appears to be two use cases for "synchronization":
>>
>>   1.  Constructing and enforcing Application authorization models -  A=
n application (acting as a SCIM client) caches users/groups data from the=
 IdP in order to present "user/group pickers" when presenting screens use=
d to configure the application  authorization rules (RBAC, Policy, or ACL=
).  Also, when the application enforces authorization, user and group dat=
a needs to be immediately available so that authorization decisions can b=
e made quickly.
>>
>>   2.  Identity Management and Governance systems - implement a canonic=
al identity model" where all accounts and groups are represented.  This m=
odel is used to build provisioning rules and calculate separation of duty=
 violations, attestations, and approvals etc.   Management-time evaluatio=
n of the model needs to be done efficiently without external calls to the=
 SCIM service provider.
>>
>> Both above use cases, are "client-cache" use cases that need only a "o=
ne-way" sync (from the SCIM server to the SCIM client).   To accomplish t=
here are two distinct steps:  a) download the initial results (users/grou=
ps) and, b) keep the cached copy of these initial results (user/groups) u=
p to date with changes that are being made on the SCIM Service provider.
>>
>> I think it could help us narrow down the list of suitable approaches i=
f we could agree that "one-way" sync (keeping a client-side cache up to d=
ate) is our target.
>>
>> --
>> Matt Peterson
>>
>> -----Original Message-----
>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>> Sent: Wednesday, August 18, 2021 8:34 AM
>> To: SCIM WG <scim@ietf.org>
>> Subject: [scim] SCIM Synchronization Problem
>>
>> CAUTION: This email originated from outside of the organization. Do no=
t follow guidance, click links, or open attachments unless you recognize =
the sender and know the content is safe.
>>
>>
>> I decided that this needs it's own thread and not be part of the meeti=
ng minutes.
>>
>> I have had a great deal of experience dealing with the user account sy=
nchronization problem. Here's my view of the problems.
>>
>> I will be calling one system Management Server and the other system Ap=
plication Server. I found client/server labels confusing. The Management =
Server is what I am defining to be the server that sends updates to add/u=
pdate/remove users and groups to the Application server whose account, gr=
oups and access permissions are being managed.
>>
>> First some definitions of user accounts. There are usually more than o=
ne of each of these:
>> 1. Builtin accounts
>> 2. Special-purpose accounts
>> 3. Employee
>> 4. Contractor
>> 5. Agent
>> 6. Customer
>>
>> There may be more.
>>
>> 1. Builtin accounts: These are accounts that applications have and the=
re may be more than one. There is always an admin account which can do an=
ything, for example the administrator account in Active Directory or a da=
tabase admin account. The application may have more accounts for other pu=
rposes.
>>
>> 2. Special-purpose accounts: These may be set up to provide access to =
other applications, for example a SCIM request to a SCIM REST API should =
be handled by a special account which cannot be used to login via a UI in=
terface and only be able to perform certain functions. In addition there =
may be accounts set up to listen for topics or queues on a message queue =
among other possibilities. Keeping separate accounts like this are import=
ant for tracking in logs and applications.
>>
>> 3. Employee: These are accounts that employees may login to the applic=
ation.
>>
>> 4. Contractors: These accounts that a contractor performing work for t=
he company may use to log into an application. Unlike Employee accounts t=
hese would have an expiration date.
>>
>> 5. Agent: Accounts like this are for external users who may need to ma=
nage information for their own customers. An example of this is an insura=
nce agent logging in to handle an insurance policy for their clients.
>>
>> 6. Customers: These are where the customers are using the application =
directly. For a bank it's likely to be millions of customers. The managem=
ent platform should not be involved in managing these accounts.
>>
>> Let's now look at a few example applications.
>>
>> 1. Helpdesk
>> All employees and contractors will need to be able to log into a helpd=
esk application and enter tickets. This means loading information about a=
ll employees and contractors. For a company with only 1000 employees that=
's manageable. For a company with 100K employees, it's a bigger challenge=
=2E
>>
>> 2. Customer Support
>> Only employees or contractors in the department providing customer sup=
port need access plus a few other employees. In addition identified custo=
mers may need accounts.
>>
>> 3. Expenses
>> Not all employees or contractors will be submitting expenses so it may=
 not be necessary to have accounts for all possible users. This is someth=
ing that the application owner needs to decide.
>>
>> Now let's look at logistics.
>>
>> Bulk load:
>> Each application will need an initial set of accounts set up and for s=
omething like a helpdesk this could involve load 1000-100,000 accounts.
>> The information needed could come from either the management server or=
 separately, say from an HR system. Many servers that I have encountered =
limit the number of records to something like 1000, so the pagination req=
uirement is needed for this. Even when dealing with a limited subset of e=
mployees or contractors you can run into this need.
>>
>> Synchronization
>> An application that is bulk-loaded above may need to be synchronized t=
o the management server if the data did not come from the management serv=
er.
>>
>> Change Management
>> This is really a synchronization issue as well. Changes happen all the=
 time and new employees/contractors need to be added, terminated ones rem=
oved and updates happen all the time. The best way of dealing with this m=
ay be to set up a message queue that each application can subscribe to an=
d they can take the needed action when it's convenient for that applicati=
on. It's not the only method but it's the one I found to be the most help=
ful. There are two ways of doing that: 1. send the complete user informat=
ion for new accounts, send just the change for updating accounts, send th=
e ID for terminated accounts along with some meta information. The other =
method which I have used is just to send the ID and whether it's new, upd=
ated or terminated.
>>
>> I hope this is helpful to the discussion.
>>
>> Danny
>>
>>
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fww=
w.ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterson=
%40quest.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c186=
7ec606603%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC=
4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=
=3DriJQy3jEHltc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0
>>
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://www.ietf.org/mailman/listinfo/scim


From nobody Fri Aug 20 08:31:54 2021
Return-Path: <phil.hunt@independentid.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 915A53A10C5 for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 08:31:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 kB7gC6c_VAYd for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 08:31:47 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 205783A10CC for <scim@ietf.org>; Fri, 20 Aug 2021 08:31:47 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id oa17so7571943pjb.1 for <scim@ietf.org>; Fri, 20 Aug 2021 08:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=jme/kP3xZoLqmc+QznNwfQHzzgzm6Ufk66BwIXcRcEI=; b=UKbnpPArHyynj7t8ugYv6u9EuEa5SWPyOz/5zh6uL0fQWaMfp2rexA4pSaoXEsLcdt +Jm7rETwKzk1yt/Dv+I2iKlZPdFAt+h36KrGy04vdyeewNKjsrYx3TQsOPynZNeEZlFi eUX8c78OI9R+fQsUT7Bv3PN+vzP5KBD2tECWeirxmr3cdo4h+2+x93zJwy4mgQ7HjFz7 j/EekXdS+OHc7gJgBb+J9VAZupLA5ouIFiw6ot4H76F3zG3qJwRE9cLS2TtD9MIBruuE jyshLBnf6bIZLgrKQZnqZ3X6PxgYoN0g8zksojaKmpHVvjdDL1VXyXwSPR9avJOUTEaa y6+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=jme/kP3xZoLqmc+QznNwfQHzzgzm6Ufk66BwIXcRcEI=; b=PHkT5SxXtq22Cg1piSdKw2XFgx2+ucRoDJk20+m375WCvE9twoU/flwcMUdkaqBmge MW+a/eQDUrPm65dV5eKmkdd28MO/YP7+PXOvSvRIJa40i6gTnAS6yE5JOIVnN4XU7Vdn 5p3ewO9yTUcqbYK516y96hDjj+aGkg1ZfxKM9ufX/BL78slNOCORkF5s7JJfiCM7/0Kq FrVmH429H4aEEYEPN84Hi+jv2h4jgnw7HP4QVYnKLXwG+f7hrwult2PF3JE6+4M7d6JN IluqhcU6LAFHLtb9Jal6VaAbwRyny7Iln/57b3ere1KEJtb5D5S5OwAacN0xttm1Ujdz rofg==
X-Gm-Message-State: AOAM531ggG6z3JYU4gX7BVM6UBQUl86s2GDHvTuSxJU/Gd8Oc3UPj8i1 q7oR2PF/GqjEImVCva+LyKopRQ==
X-Google-Smtp-Source: ABdhPJzQpz5GJSwr6m3XK5hHfD+cib0zQyyJiNy0t98lcyCEVrrEhCA1ARpRZJ2N1PEe+U8FYftHcg==
X-Received: by 2002:a17:902:e04e:b029:12c:def4:56a3 with SMTP id x14-20020a170902e04eb029012cdef456a3mr16747280plx.76.1629473505472;  Fri, 20 Aug 2021 08:31:45 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9qqo6k58q0ekapvh7n7h.ipv6.telus.net. [2001:569:79bc:100:e131:bc00:c956:e3d]) by smtp.gmail.com with ESMTPSA id b8sm6562985pjo.51.2021.08.20.08.31.44 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 Aug 2021 08:31:44 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Fri, 20 Aug 2021 08:31:43 -0700
Message-Id: <6E006C03-06E0-4488-983E-0E0357B14363@independentid.com>
References: <b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net>
Cc: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>, SCIM WG <scim@ietf.org>
In-Reply-To: <b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net>
To: Danny Mayer <mayer@pdmconsulting.net>
X-Mailer: iPhone Mail (18G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/cbre5YRzo05hk0QaTy1m8fVGH6I>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 15:31:53 -0000

To be clear, the specs are written as protocol profiling HTTP.  The terms cl=
ient and server stem from HTTP=E2=80=99s notion that a client initiates a re=
quest and a server responds.=20

It is ok to develop a higher level in the information layer.  For example we=
 had to adopt publish and subscribe for security events flow but the deliver=
y specs talk about whether subscribers act as http clients or servers depend=
ing in whether events are pushed to them or whether they pull events from th=
e publisher.=20

Some of Danny=E2=80=99s requirements strike me as access control needs in sc=
im service.  For example a client that authenticates with the correct scope m=
ay be allowed to return unlimited results in a request or may be allowed fre=
quent polling requests. Another client may only be allowed to update or read=
 specific claims at a certain rate.   Access control is something we can tal=
k about in the charter (I have a proposal I can put together quickly in a dr=
aft)) but I would not support conflating access control with synchronization=
. =20

The cases Danny is describing sound like a hybrid (of replica vs coordinated=
) where two domains are unequal but under a common authority.  This of cours=
e should be supported.=20

The event model helps responsiveness in that subscribers can register to lis=
ten for changes as they occur.  As I mentioned previously I am happy to give=
 a presentation on synchronous command (ie REST) vs async events and why thi=
s aids cross-domain synchronization performance and accuracy.=20

Phil

> On Aug 20, 2021, at 8:04 AM, Danny Mayer <mayer@pdmconsulting.net> wrote:
>=20
> =EF=BB=BFYou cannot assume that the groups are the same across different a=
pplication domains. In our case each group was totally different and had dif=
ferent permissions associated with it. In addition you can have different pe=
rmissions associated individually to a user account. Microsoft's NTFS access=
 controls are a good example of this.
>=20
> The SCIM Config information should include information on what commands ar=
e available on that system. In addition the application needs to notify the r=
equestor that if something went wrong why it went wrong. For example, in my c=
ases if a request for a group to be added to a user cannot be fulfilled beca=
use the group does not exist then the failure needs to be reported back. Als=
o for our builtin and special accounts, the requestor cannot make any change=
s.
>=20
> Does this help?
>=20
> Danny
>=20
>> On 8/19/21 2:05 PM, Phillip Hunt wrote:
>> This is good high level case information.
>>=20
>> Matt, you make a good case for access control standards. It brings out so=
me questions=E2=80=A6
>>=20
>> Is syncing users and groups enough or must access policy rules/data be sy=
nchronized (assuming a common standard for policy)?  How close must separate=
 domains be to work this well together? Is it true that access control is th=
e same across domains?
>>=20
>> These issues are what led me to believe client/server RESTful =E2=80=9Cco=
mmand=E2=80=9Ds like POST/PUT/PATCH are insufficient. Instead, what if an ev=
ent in one domain is published and a subscriber decides how to process the e=
vent? In command mode the requestor has to know the command will work. In ev=
ent mode, the receiver has context to interpret and translate into local com=
mands.
>>=20
>> Maybe we can do a con call and go through security events and how they su=
pport arms length cross domain relationships.
>>=20
>> Phil
>>=20
>>>> On Aug 19, 2021, at 10:33 AM, Matt Peterson (mpeterso) <Matt.Peterson=3D=
40oneidentity.com@dmarc.ietf.org> wrote:
>>>=20
>>> =EF=BB=BFThank you, Danny, for creating a new thread.  The following are=
 my comments from meeting minutes (some edits):
>>>=20
>>> There appears to be two use cases for "synchronization":
>>>=20
>>>  1.  Constructing and enforcing Application authorization models -  An a=
pplication (acting as a SCIM client) caches users/groups data from the IdP i=
n order to present "user/group pickers" when presenting screens used to conf=
igure the application  authorization rules (RBAC, Policy, or ACL).  Also, wh=
en the application enforces authorization, user and group data needs to be i=
mmediately available so that authorization decisions can be made quickly.
>>>=20
>>>  2.  Identity Management and Governance systems - implement a canonical i=
dentity model" where all accounts and groups are represented.  This model is=
 used to build provisioning rules and calculate separation of duty violation=
s, attestations, and approvals etc.   Management-time evaluation of the mode=
l needs to be done efficiently without external calls to the SCIM service pr=
ovider.
>>>=20
>>> Both above use cases, are "client-cache" use cases that need only a "one=
-way" sync (from the SCIM server to the SCIM client).   To accomplish there a=
re two distinct steps:  a) download the initial results (users/groups) and, b=
) keep the cached copy of these initial results (user/groups) up to date wit=
h changes that are being made on the SCIM Service provider.
>>>=20
>>> I think it could help us narrow down the list of suitable approaches if w=
e could agree that "one-way" sync (keeping a client-side cache up to date) i=
s our target.
>>>=20
>>> --
>>> Matt Peterson
>>>=20
>>> -----Original Message-----
>>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>>> Sent: Wednesday, August 18, 2021 8:34 AM
>>> To: SCIM WG <scim@ietf.org>
>>> Subject: [scim] SCIM Synchronization Problem
>>>=20
>>> CAUTION: This email originated from outside of the organization. Do not f=
ollow guidance, click links, or open attachments unless you recognize the se=
nder and know the content is safe.
>>>=20
>>>=20
>>> I decided that this needs it's own thread and not be part of the meeting=
 minutes.
>>>=20
>>> I have had a great deal of experience dealing with the user account sync=
hronization problem. Here's my view of the problems.
>>>=20
>>> I will be calling one system Management Server and the other system Appl=
ication Server. I found client/server labels confusing. The Management Serve=
r is what I am defining to be the server that sends updates to add/update/re=
move users and groups to the Application server whose account, groups and ac=
cess permissions are being managed.
>>>=20
>>> First some definitions of user accounts. There are usually more than one=
 of each of these:
>>> 1. Builtin accounts
>>> 2. Special-purpose accounts
>>> 3. Employee
>>> 4. Contractor
>>> 5. Agent
>>> 6. Customer
>>>=20
>>> There may be more.
>>>=20
>>> 1. Builtin accounts: These are accounts that applications have and there=
 may be more than one. There is always an admin account which can do anythin=
g, for example the administrator account in Active Directory or a database a=
dmin account. The application may have more accounts for other purposes.
>>>=20
>>> 2. Special-purpose accounts: These may be set up to provide access to ot=
her applications, for example a SCIM request to a SCIM REST API should be ha=
ndled by a special account which cannot be used to login via a UI interface a=
nd only be able to perform certain functions. In addition there may be accou=
nts set up to listen for topics or queues on a message queue among other pos=
sibilities. Keeping separate accounts like this are important for tracking i=
n logs and applications.
>>>=20
>>> 3. Employee: These are accounts that employees may login to the applicat=
ion.
>>>=20
>>> 4. Contractors: These accounts that a contractor performing work for the=
 company may use to log into an application. Unlike Employee accounts these w=
ould have an expiration date.
>>>=20
>>> 5. Agent: Accounts like this are for external users who may need to mana=
ge information for their own customers. An example of this is an insurance a=
gent logging in to handle an insurance policy for their clients.
>>>=20
>>> 6. Customers: These are where the customers are using the application di=
rectly. For a bank it's likely to be millions of customers. The management p=
latform should not be involved in managing these accounts.
>>>=20
>>> Let's now look at a few example applications.
>>>=20
>>> 1. Helpdesk
>>> All employees and contractors will need to be able to log into a helpdes=
k application and enter tickets. This means loading information about all em=
ployees and contractors. For a company with only 1000 employees that's manag=
eable. For a company with 100K employees, it's a bigger challenge.
>>>=20
>>> 2. Customer Support
>>> Only employees or contractors in the department providing customer suppo=
rt need access plus a few other employees. In addition identified customers m=
ay need accounts.
>>>=20
>>> 3. Expenses
>>> Not all employees or contractors will be submitting expenses so it may n=
ot be necessary to have accounts for all possible users. This is something t=
hat the application owner needs to decide.
>>>=20
>>> Now let's look at logistics.
>>>=20
>>> Bulk load:
>>> Each application will need an initial set of accounts set up and for som=
ething like a helpdesk this could involve load 1000-100,000 accounts.
>>> The information needed could come from either the management server or s=
eparately, say from an HR system. Many servers that I have encountered limit=
 the number of records to something like 1000, so the pagination requirement=
 is needed for this. Even when dealing with a limited subset of employees or=
 contractors you can run into this need.
>>>=20
>>> Synchronization
>>> An application that is bulk-loaded above may need to be synchronized to t=
he management server if the data did not come from the management server.
>>>=20
>>> Change Management
>>> This is really a synchronization issue as well. Changes happen all the t=
ime and new employees/contractors need to be added, terminated ones removed a=
nd updates happen all the time. The best way of dealing with this may be to s=
et up a message queue that each application can subscribe to and they can ta=
ke the needed action when it's convenient for that application. It's not the=
 only method but it's the one I found to be the most helpful. There are two w=
ays of doing that: 1. send the complete user information for new accounts, s=
end just the change for updating accounts, send the ID for terminated accoun=
ts along with some meta information. The other method which I have used is j=
ust to send the ID and whether it's new, updated or terminated.
>>>=20
>>> I hope this is helpful to the discussion.
>>>=20
>>> Danny
>>>=20
>>>=20
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7Cmatt.peterson%40qu=
est.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec60660=
3%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL=
CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DriJQy3jEHlt=
c6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=3D0
>>>=20
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/scim
>=20


From nobody Fri Aug 20 09:44:58 2021
Return-Path: <mayer@pdmconsulting.net>
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 48A4E3A1598 for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 DBzXcx0pE1Lz for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 128DB3A159B for <scim@ietf.org>; Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GrnYB5BnmzMNWd; Fri, 20 Aug 2021 16:44:46 +0000 (UTC)
To: Phillip Hunt <phil.hunt@independentid.com>
Cc: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>, SCIM WG <scim@ietf.org>
References: <b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net> <6E006C03-06E0-4488-983E-0E0357B14363@independentid.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <f1f49a63-b82d-fc50-96a1-a13ac46a022d@pdmconsulting.net>
Date: Fri, 20 Aug 2021 12:44:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <6E006C03-06E0-4488-983E-0E0357B14363@independentid.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/tyYmMwLCkML2PHcc4TcNoTEMbn4>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 16:44:56 -0000

The cases I was describing were exactly access and permissions cases and 
was needed for audit and compliance purposes. In our cases the groups 
that were associated with the user accounts provided the permissions 
needed for each user.

Danny

On 8/20/21 11:31 AM, Phillip Hunt wrote:
> To be clear, the specs are written as protocol profiling HTTP.  The terms client and server stem from HTTP’s notion that a client initiates a request and a server responds.
>
> It is ok to develop a higher level in the information layer.  For example we had to adopt publish and subscribe for security events flow but the delivery specs talk about whether subscribers act as http clients or servers depending in whether events are pushed to them or whether they pull events from the publisher.
>
> Some of Danny’s requirements strike me as access control needs in scim service.  For example a client that authenticates with the correct scope may be allowed to return unlimited results in a request or may be allowed frequent polling requests. Another client may only be allowed to update or read specific claims at a certain rate.   Access control is something we can talk about in the charter (I have a proposal I can put together quickly in a draft)) but I would not support conflating access control with synchronization.
>
> The cases Danny is describing sound like a hybrid (of replica vs coordinated) where two domains are unequal but under a common authority.  This of course should be supported.
>
> The event model helps responsiveness in that subscribers can register to listen for changes as they occur.  As I mentioned previously I am happy to give a presentation on synchronous command (ie REST) vs async events and why this aids cross-domain synchronization performance and accuracy.
>
> Phil
>
>> On Aug 20, 2021, at 8:04 AM, Danny Mayer <mayer@pdmconsulting.net> wrote:
>>
>> ﻿You cannot assume that the groups are the same across different application domains. In our case each group was totally different and had different permissions associated with it. In addition you can have different permissions associated individually to a user account. Microsoft's NTFS access controls are a good example of this.
>>
>> The SCIM Config information should include information on what commands are available on that system. In addition the application needs to notify the requestor that if something went wrong why it went wrong. For example, in my cases if a request for a group to be added to a user cannot be fulfilled because the group does not exist then the failure needs to be reported back. Also for our builtin and special accounts, the requestor cannot make any changes.
>>
>> Does this help?
>>
>> Danny
>>
>>> On 8/19/21 2:05 PM, Phillip Hunt wrote:
>>> This is good high level case information.
>>>
>>> Matt, you make a good case for access control standards. It brings out some questions…
>>>
>>> Is syncing users and groups enough or must access policy rules/data be synchronized (assuming a common standard for policy)?  How close must separate domains be to work this well together? Is it true that access control is the same across domains?
>>>
>>> These issues are what led me to believe client/server RESTful “command”s like POST/PUT/PATCH are insufficient. Instead, what if an event in one domain is published and a subscriber decides how to process the event? In command mode the requestor has to know the command will work. In event mode, the receiver has context to interpret and translate into local commands.
>>>
>>> Maybe we can do a con call and go through security events and how they support arms length cross domain relationships.
>>>
>>> Phil
>>>
>>>>> On Aug 19, 2021, at 10:33 AM, Matt Peterson (mpeterso) <Matt.Peterson=40oneidentity.com@dmarc.ietf.org> wrote:
>>>> ﻿Thank you, Danny, for creating a new thread.  The following are my comments from meeting minutes (some edits):
>>>>
>>>> There appears to be two use cases for "synchronization":
>>>>
>>>>   1.  Constructing and enforcing Application authorization models -  An application (acting as a SCIM client) caches users/groups data from the IdP in order to present "user/group pickers" when presenting screens used to configure the application  authorization rules (RBAC, Policy, or ACL).  Also, when the application enforces authorization, user and group data needs to be immediately available so that authorization decisions can be made quickly.
>>>>
>>>>   2.  Identity Management and Governance systems - implement a canonical identity model" where all accounts and groups are represented.  This model is used to build provisioning rules and calculate separation of duty violations, attestations, and approvals etc.   Management-time evaluation of the model needs to be done efficiently without external calls to the SCIM service provider.
>>>>
>>>> Both above use cases, are "client-cache" use cases that need only a "one-way" sync (from the SCIM server to the SCIM client).   To accomplish there are two distinct steps:  a) download the initial results (users/groups) and, b) keep the cached copy of these initial results (user/groups) up to date with changes that are being made on the SCIM Service provider.
>>>>
>>>> I think it could help us narrow down the list of suitable approaches if we could agree that "one-way" sync (keeping a client-side cache up to date) is our target.
>>>>
>>>> --
>>>> Matt Peterson
>>>>
>>>> -----Original Message-----
>>>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>>>> Sent: Wednesday, August 18, 2021 8:34 AM
>>>> To: SCIM WG <scim@ietf.org>
>>>> Subject: [scim] SCIM Synchronization Problem
>>>>
>>>> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>>>>
>>>>
>>>> I decided that this needs it's own thread and not be part of the meeting minutes.
>>>>
>>>> I have had a great deal of experience dealing with the user account synchronization problem. Here's my view of the problems.
>>>>
>>>> I will be calling one system Management Server and the other system Application Server. I found client/server labels confusing. The Management Server is what I am defining to be the server that sends updates to add/update/remove users and groups to the Application server whose account, groups and access permissions are being managed.
>>>>
>>>> First some definitions of user accounts. There are usually more than one of each of these:
>>>> 1. Builtin accounts
>>>> 2. Special-purpose accounts
>>>> 3. Employee
>>>> 4. Contractor
>>>> 5. Agent
>>>> 6. Customer
>>>>
>>>> There may be more.
>>>>
>>>> 1. Builtin accounts: These are accounts that applications have and there may be more than one. There is always an admin account which can do anything, for example the administrator account in Active Directory or a database admin account. The application may have more accounts for other purposes.
>>>>
>>>> 2. Special-purpose accounts: These may be set up to provide access to other applications, for example a SCIM request to a SCIM REST API should be handled by a special account which cannot be used to login via a UI interface and only be able to perform certain functions. In addition there may be accounts set up to listen for topics or queues on a message queue among other possibilities. Keeping separate accounts like this are important for tracking in logs and applications.
>>>>
>>>> 3. Employee: These are accounts that employees may login to the application.
>>>>
>>>> 4. Contractors: These accounts that a contractor performing work for the company may use to log into an application. Unlike Employee accounts these would have an expiration date.
>>>>
>>>> 5. Agent: Accounts like this are for external users who may need to manage information for their own customers. An example of this is an insurance agent logging in to handle an insurance policy for their clients.
>>>>
>>>> 6. Customers: These are where the customers are using the application directly. For a bank it's likely to be millions of customers. The management platform should not be involved in managing these accounts.
>>>>
>>>> Let's now look at a few example applications.
>>>>
>>>> 1. Helpdesk
>>>> All employees and contractors will need to be able to log into a helpdesk application and enter tickets. This means loading information about all employees and contractors. For a company with only 1000 employees that's manageable. For a company with 100K employees, it's a bigger challenge.
>>>>
>>>> 2. Customer Support
>>>> Only employees or contractors in the department providing customer support need access plus a few other employees. In addition identified customers may need accounts.
>>>>
>>>> 3. Expenses
>>>> Not all employees or contractors will be submitting expenses so it may not be necessary to have accounts for all possible users. This is something that the application owner needs to decide.
>>>>
>>>> Now let's look at logistics.
>>>>
>>>> Bulk load:
>>>> Each application will need an initial set of accounts set up and for something like a helpdesk this could involve load 1000-100,000 accounts.
>>>> The information needed could come from either the management server or separately, say from an HR system. Many servers that I have encountered limit the number of records to something like 1000, so the pagination requirement is needed for this. Even when dealing with a limited subset of employees or contractors you can run into this need.
>>>>
>>>> Synchronization
>>>> An application that is bulk-loaded above may need to be synchronized to the management server if the data did not come from the management server.
>>>>
>>>> Change Management
>>>> This is really a synchronization issue as well. Changes happen all the time and new employees/contractors need to be added, terminated ones removed and updates happen all the time. The best way of dealing with this may be to set up a message queue that each application can subscribe to and they can take the needed action when it's convenient for that application. It's not the only method but it's the one I found to be the most helpful. There are two ways of doing that: 1. send the complete user information for new accounts, send just the change for updating accounts, send the ID for terminated accounts along with some meta information. The other method which I have used is just to send the ID and whether it's new, updated or terminated.
>>>>
>>>> I hope this is helpful to the discussion.
>>>>
>>>> Danny
>>>>
>>>>
>>>> _______________________________________________
>>>> scim mailing list
>>>> scim@ietf.org
>>>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7Cmatt.peterson%40quest.com%7C1fb1fe803b8c439026bd08d9625553ba%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637648940889425726%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=riJQy3jEHltc6ZFCaEe%2B6%2F2ecXN0SWBXOxIZAKLxum4%3D&amp;reserved=0
>>>>
>>>> _______________________________________________
>>>> scim mailing list
>>>> scim@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/scim


From nobody Fri Aug 20 09:51:04 2021
Return-Path: <mayer@pdmconsulting.net>
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 72F1F3A15D0 for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 09:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 G-hwgFge1zAQ for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 09:50:55 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FD233A15CE for <scim@ietf.org>; Fri, 20 Aug 2021 09:50:52 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GrnhC1rVpzMNWd for <scim@ietf.org>; Fri, 20 Aug 2021 16:50:51 +0000 (UTC)
References: <7e4a6808-f0d2-4389-a671-3b3a414f913f@M4W0334.microfocus.com>
To: SCIM WG <scim@ietf.org>
From: Danny Mayer <mayer@pdmconsulting.net>
X-Forwarded-Message-Id: <7e4a6808-f0d2-4389-a671-3b3a414f913f@M4W0334.microfocus.com>
Message-ID: <af221302-cd31-85b3-ee2a-15e1a82ca452@pdmconsulting.net>
Date: Fri, 20 Aug 2021 12:50:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <7e4a6808-f0d2-4389-a671-3b3a414f913f@M4W0334.microfocus.com>
Content-Type: multipart/alternative; boundary="------------21CAA9F75771EAACC707C1D1"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/_Ez-78aY7hcAFLDrEpv3RIspFbg>
Subject: [scim] Fwd: Non-existent address
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 20 Aug 2021 16:51:03 -0000

This is a multi-part message in MIME format.
--------------21CAA9F75771EAACC707C1D1
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Can whoever is authorized remove this address from the mailing list? 
Apparently it no longer exists.

Thanks,

Danny


-------- Forwarded Message --------
Subject: 	Undeliverable: Re: [scim] SCIM Synchronization Problem
Date: 	Fri, 20 Aug 2021 16:45:10 +0000
From: 	postmaster@microfocus.com
To: 	mayer@pdmconsulting.net



*Delivery has failed to these recipients or groups:*

groupwise-aditya.vikram@microfocus.com 
<mailto:groupwise-aditya.vikram@microfocus.com>
The email address you entered couldn't be found. Please check the 
recipient's email address and try to resend the message. If the problem 
continues, please contact your email admin.







*Diagnostic information for administrators:*

Generating server: M4W0334.microfocus.com

groupwise-aditya.vikram@microfocus.com
Remote Server returned '550 5.1.10 RESOLVER.ADR.RecipientNotFound; 
Recipient not found by SMTP address lookup'

Original message headers:

Received: from M4W0335.microfocus.com (2002:f78:1193::f78:1193) by
  M4W0334.microfocus.com (2002:f78:1192::f78:1192) with Microsoft SMTP Server
  (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
  15.1.2176.14; Fri, 20 Aug 2021 16:45:09 +0000
Received: from prv-mh.provo.novell.com (137.65.248.74) by
  M4W0335.microfocus.com (15.120.17.147) with Microsoft SMTP Server
  (version=TLS1_2, cipher=TLS_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2176.14 via
  Frontend Transport; Fri, 20 Aug 2021 16:45:10 +0000
Received: from INET-PRV-MTA by prv-mh.provo.novell.com
	with Novell_GroupWise; Fri, 20 Aug 2021 10:45:08 -0600
Return-Path: mayer@pdmconsulting.net
Received: from m4a0087g.houston.softwaregrp.com ([15.124.2.137])
	by prv-mh.provo.novell.com with ESMTP (TLS encrypted); Fri, 20 Aug 2021 10:45:06 -0600
Received: FROM m4a0087g.houston.softwaregrp.com (4.31.198.44) BY m4a0087g.houston.softwaregrp.com WITH ESMTP
  FOR avikram@novell.com;
  Fri, 20 Aug 2021 16:44:13 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 13EDC3A15A9
	for <avikram@novell.com>; Fri, 20 Aug 2021 09:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1629477904; bh=Y2Q7refn2f8jsTWkrIndvZ6RM9lWySAcvbE3UhI5MHY=;
	h=To:References:From:Date:In-Reply-To:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Cc;
	b=E+IanJCcjF6yVdADMOeaaGgRgLvHFs2tXyc+lhVUUByXOBpHri3NcHds6FkG1iD0n
	 cwT2UWx1sRGwOKIRA+d1Id1lV3P4o7S6Lhv3+EIkEAPcSBcV30q12IyUh7pSg93Eof
	 41u1yqXaP3X/H02NSNp3mLsleyt5yjaxBmTUKkXc=
X-Mailbox-Line: From scim-bounces@ietf.org  Fri Aug 20 09:45:00 2021
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 289483A159E;
	Fri, 20 Aug 2021 09:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1629477899; bh=Y2Q7refn2f8jsTWkrIndvZ6RM9lWySAcvbE3UhI5MHY=;
	h=To:References:From:Date:In-Reply-To:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Cc;
	b=JOD/gCNG42d6z1O16rzNAGLcNP7CbRf89nDJTVQyg3oDuPVTW1teRV3ciz5F61VrA
	 ItvQ9reEVb0iIzbF5TARDywRwtdEGfTEki/xzYeu84q60OGi9masOqqFSGrxW0ZACj
	 uJyqNKyhWhWjIJm1gLFPBe8BSBV8pW1WBm1ZeR3A=
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 48A4E3A1598
  for <scim@ietfa.amsl.com>; Fri, 20 Aug 2021 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5
  tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001,
  URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 DBzXcx0pE1Lz for <scim@ietfa.amsl.com>;
  Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org
  [IPv6:2001:470:1:205::234])
  (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
  (No client certificate requested)
  by ietfa.amsl.com (Postfix) with ESMTPS id 128DB3A159B
  for <scim@ietf.org>; Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from newusers-MBP.fios-router.home
  (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179])
  (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
  key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
  (No client certificate requested)
  by chessie.everett.org (Postfix) with ESMTPSA id 4GrnYB5BnmzMNWd;
  Fri, 20 Aug 2021 16:44:46 +0000 (UTC)
From: Danny Mayer <mayer@pdmconsulting.net>
To: Phillip Hunt <phil.hunt@independentid.com>
CC: "Matt Peterson (mpeterso)"
	<Matt.Peterson=40oneidentity.com@dmarc.ietf.org>, SCIM WG <scim@ietf.org>
References: <b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net>
  <6E006C03-06E0-4488-983E-0E0357B14363@independentid.com>
Message-ID: <f1f49a63-b82d-fc50-96a1-a13ac46a022d@pdmconsulting.net>
Date: Fri, 20 Aug 2021 12:44:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
  Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/tyYmMwLCkML2PHcc4TcNoTEMbn4>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; format=flowed
Errors-To: scim-bounces@ietf.org
Sender: scim <scim-bounces@ietf.org>


--------------21CAA9F75771EAACC707C1D1
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=windows-1252">
  </head>
  <body>
    <p>Can whoever is authorized remove this address from the mailing
      list? Apparently it no longer exists.</p>
    <p>Thanks,</p>
    <p>Danny<br>
    </p>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>Undeliverable: Re: [scim] SCIM Synchronization Problem</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Fri, 20 Aug 2021 16:45:10 +0000</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:postmaster@microfocus.com">postmaster@microfocus.com</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:mayer@pdmconsulting.net">mayer@pdmconsulting.net</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <p><b><font size="3" face="Arial" color="#000066">Delivery has
            failed to these recipients or groups:</font></b></p>
      <p><font size="2" face="Tahoma" color="#000000"><a
            href="mailto:groupwise-aditya.vikram@microfocus.com"
            moz-do-not-send="true">groupwise-aditya.vikram@microfocus.com</a><br>
        </font>
        <font size="3" face="Arial" color="#000000">The email address
          you entered couldn't be found. Please check the recipient's
          email address and try to resend the message. If the problem
          continues, please contact your email admin.<br>
        </font>
        <font size="2" face="Tahoma" color="#000000"><br>
        </font></p>
      <font size="2" face="Tahoma" color="#000000">
      </font>
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      <font size="2" face="Tahoma" color="#808080">
        <p><b>Diagnostic information for administrators:</b></p>
        <p>Generating server: M4W0334.microfocus.com<br>
        </p>
        <p><a class="moz-txt-link-abbreviated" href="mailto:groupwise-aditya.vikram@microfocus.com">groupwise-aditya.vikram@microfocus.com</a><br>
          Remote Server returned '550 5.1.10
          RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP
          address lookup'<br>
        </p>
        <p>Original message headers:</p>
        <pre>Received: from M4W0335.microfocus.com (2002:f78:1193::f78:1193) by
 M4W0334.microfocus.com (2002:f78:1192::f78:1192) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
 15.1.2176.14; Fri, 20 Aug 2021 16:45:09 +0000
Received: from prv-mh.provo.novell.com (137.65.248.74) by
 M4W0335.microfocus.com (15.120.17.147) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2176.14 via
 Frontend Transport; Fri, 20 Aug 2021 16:45:10 +0000
Received: from INET-PRV-MTA by prv-mh.provo.novell.com
	with Novell_GroupWise; Fri, 20 Aug 2021 10:45:08 -0600
Return-Path: <a class="moz-txt-link-abbreviated" href="mailto:mayer@pdmconsulting.net">mayer@pdmconsulting.net</a>
Received: from m4a0087g.houston.softwaregrp.com ([15.124.2.137])
	by prv-mh.provo.novell.com with ESMTP (TLS encrypted); Fri, 20 Aug 2021 10:45:06 -0600
Received: FROM m4a0087g.houston.softwaregrp.com (4.31.198.44) BY m4a0087g.houston.softwaregrp.com WITH ESMTP
 FOR <a class="moz-txt-link-abbreviated" href="mailto:avikram@novell.com">avikram@novell.com</a>;
 Fri, 20 Aug 2021 16:44:13 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 13EDC3A15A9
	for <a class="moz-txt-link-rfc2396E" href="mailto:avikram@novell.com">&lt;avikram@novell.com&gt;</a>; Fri, 20 Aug 2021 09:45:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1629477904; bh=Y2Q7refn2f8jsTWkrIndvZ6RM9lWySAcvbE3UhI5MHY=;
	h=To:References:From:Date:In-Reply-To:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Cc;
	b=E+IanJCcjF6yVdADMOeaaGgRgLvHFs2tXyc+lhVUUByXOBpHri3NcHds6FkG1iD0n
	 cwT2UWx1sRGwOKIRA+d1Id1lV3P4o7S6Lhv3+EIkEAPcSBcV30q12IyUh7pSg93Eof
	 41u1yqXaP3X/H02NSNp3mLsleyt5yjaxBmTUKkXc=
X-Mailbox-Line: From <a class="moz-txt-link-abbreviated" href="mailto:scim-bounces@ietf.org">scim-bounces@ietf.org</a>  Fri Aug 20 09:45:00 2021
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 289483A159E;
	Fri, 20 Aug 2021 09:44:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1629477899; bh=Y2Q7refn2f8jsTWkrIndvZ6RM9lWySAcvbE3UhI5MHY=;
	h=To:References:From:Date:In-Reply-To:Subject:List-Id:
	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
	 Cc;
	b=JOD/gCNG42d6z1O16rzNAGLcNP7CbRf89nDJTVQyg3oDuPVTW1teRV3ciz5F61VrA
	 ItvQ9reEVb0iIzbF5TARDywRwtdEGfTEki/xzYeu84q60OGi9masOqqFSGrxW0ZACj
	 uJyqNKyhWhWjIJm1gLFPBe8BSBV8pW1WBm1ZeR3A=
X-Original-To: <a class="moz-txt-link-abbreviated" href="mailto:scim@ietfa.amsl.com">scim@ietfa.amsl.com</a>
Delivered-To: <a class="moz-txt-link-abbreviated" href="mailto:scim@ietfa.amsl.com">scim@ietfa.amsl.com</a>
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 48A4E3A1598
 for <a class="moz-txt-link-rfc2396E" href="mailto:scim@ietfa.amsl.com">&lt;scim@ietfa.amsl.com&gt;</a>; Fri, 20 Aug 2021 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001,
 URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 DBzXcx0pE1Lz for <a class="moz-txt-link-rfc2396E" href="mailto:scim@ietfa.amsl.com">&lt;scim@ietfa.amsl.com&gt;</a>;
 Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org
 [IPv6:2001:470:1:205::234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 128DB3A159B
 for <a class="moz-txt-link-rfc2396E" href="mailto:scim@ietf.org">&lt;scim@ietf.org&gt;</a>; Fri, 20 Aug 2021 09:44:51 -0700 (PDT)
Received: from newusers-MBP.fios-router.home
 (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by chessie.everett.org (Postfix) with ESMTPSA id 4GrnYB5BnmzMNWd;
 Fri, 20 Aug 2021 16:44:46 +0000 (UTC)
From: Danny Mayer <a class="moz-txt-link-rfc2396E" href="mailto:mayer@pdmconsulting.net">&lt;mayer@pdmconsulting.net&gt;</a>
To: Phillip Hunt <a class="moz-txt-link-rfc2396E" href="mailto:phil.hunt@independentid.com">&lt;phil.hunt@independentid.com&gt;</a>
CC: "Matt Peterson (mpeterso)"
	<a class="moz-txt-link-rfc2396E" href="mailto:Matt.Peterson=40oneidentity.com@dmarc.ietf.org">&lt;Matt.Peterson=40oneidentity.com@dmarc.ietf.org&gt;</a>, SCIM WG <a class="moz-txt-link-rfc2396E" href="mailto:scim@ietf.org">&lt;scim@ietf.org&gt;</a>
References: <a class="moz-txt-link-rfc2396E" href="mailto:b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net">&lt;b332ab98-b86d-a72c-a3c4-24e3abbddf76@pdmconsulting.net&gt;</a>
 <a class="moz-txt-link-rfc2396E" href="mailto:6E006C03-06E0-4488-983E-0E0357B14363@independentid.com">&lt;6E006C03-06E0-4488-983E-0E0357B14363@independentid.com&gt;</a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:f1f49a63-b82d-fc50-96a1-a13ac46a022d@pdmconsulting.net">&lt;f1f49a63-b82d-fc50-96a1-a13ac46a022d@pdmconsulting.net&gt;</a>
Date: Fri, 20 Aug 2021 12:44:45 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0)
 Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
Content-Language: en-US
Archived-At: <a class="moz-txt-link-rfc2396E" href="https://mailarchive.ietf.org/arch/msg/scim/tyYmMwLCkML2PHcc4TcNoTEMbn4">&lt;https://mailarchive.ietf.org/arch/msg/scim/tyYmMwLCkML2PHcc4TcNoTEMbn4&gt;</a>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: <a class="moz-txt-link-abbreviated" href="mailto:scim@ietf.org">scim@ietf.org</a>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Simple Cloud Identity Management BOF &lt;scim.ietf.org&gt;
List-Unsubscribe: <a class="moz-txt-link-rfc2396E" href="https://www.ietf.org/mailman/options/scim">&lt;https://www.ietf.org/mailman/options/scim&gt;</a>,
 <a class="moz-txt-link-rfc2396E" href="mailto:scim-request@ietf.org?subject=unsubscribe">&lt;mailto:scim-request@ietf.org?subject=unsubscribe&gt;</a>
List-Archive: <a class="moz-txt-link-rfc2396E" href="https://mailarchive.ietf.org/arch/browse/scim/">&lt;https://mailarchive.ietf.org/arch/browse/scim/&gt;</a>
List-Post: <a class="moz-txt-link-rfc2396E" href="mailto:scim@ietf.org">&lt;mailto:scim@ietf.org&gt;</a>
List-Help: <a class="moz-txt-link-rfc2396E" href="mailto:scim-request@ietf.org?subject=help">&lt;mailto:scim-request@ietf.org?subject=help&gt;</a>
List-Subscribe: <a class="moz-txt-link-rfc2396E" href="https://www.ietf.org/mailman/listinfo/scim">&lt;https://www.ietf.org/mailman/listinfo/scim&gt;</a>,
 <a class="moz-txt-link-rfc2396E" href="mailto:scim-request@ietf.org?subject=subscribe">&lt;mailto:scim-request@ietf.org?subject=subscribe&gt;</a>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; format=flowed
Errors-To: <a class="moz-txt-link-abbreviated" href="mailto:scim-bounces@ietf.org">scim-bounces@ietf.org</a>
Sender: scim <a class="moz-txt-link-rfc2396E" href="mailto:scim-bounces@ietf.org">&lt;scim-bounces@ietf.org&gt;</a>
</pre>
      </font>
    </div>
  </body>
</html>

--------------21CAA9F75771EAACC707C1D1--


From nobody Mon Aug 23 16:30:49 2021
Return-Path: <Matt.Peterson@oneidentity.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 E403C3A0A07 for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 16:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oneidentity.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 NnWnCzMg_uso for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 16:30:40 -0700 (PDT)
Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2137.outbound.protection.outlook.com [40.107.244.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0C4E3A0A00 for <scim@ietf.org>; Mon, 23 Aug 2021 16:30:35 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eNRDQznkWmZxF2oN6xvSHA0tQPzACOEaa76KhT2fyx2GGoASIXgtUj0XJE6UXF/66STHYN0mFNqTjY8dGviyNS5uAnT3PHqRXDX/MDixstNtisDfvM+qx7rAC3lU4UXxMz7rSpqagpkjNOjsFb7ALxw6jdBz0RYl7YLQlbSk7j5OW85WuuTEm1UZ7JzGWezl4czZNG/izRMeo1UMFX7NKg9Fyac5z+MfKvsaQas9VOgF8vxVk4CO5ktw4jl8K4BB4HzB9sVGy9BuD8yErT1wKGng98uc4FV9V0Dn5ut2uueCM8S1/sVIAyzXP5h0UDWtqdFPxkkz++EExDTNOKZbww==
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=FOuuEgD5waRF2nAMMkjRYPcEd9s3Cim8/GVgqfblmXA=; b=TvJUg4cyfq/l/ZqL43Ylnx9AGqTBYReukSDZLCGw/hi1uaRrAdbZ9IdbJ/xqVm0RPo6Re69ELEHESH6DPK22+2RGLTVz4xF6S8EsEUL+xYOIOF00xb2pAQ+6+JzKzcIZK0/reFJmgSYUymTpvZZVKIZsOQlWkYiqj/VN58C26s9Xic90ZxSYvKc4Mg34V6GeSuYukH516avCoTXg8GAoZwluCT+m2V5W/xGPjG3pr+E0sdvfDvqUZnU58/8M4eHL60+7IJPTaUDqEF0LVWJ4SPmmoYpQi17GOXzd5udHuqe5If1nMzcr8PUTwacSKe4ZISDz0Hl1sNvFaqcnr/QdcA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oneidentity.com; dmarc=pass action=none header.from=oneidentity.com; dkim=pass header.d=oneidentity.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oneidentity.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FOuuEgD5waRF2nAMMkjRYPcEd9s3Cim8/GVgqfblmXA=; b=cGP0w0FdZal9PZHOxrLWKFg56AJsK7J3Osw7HVGFKxPMqlaN1l7CqTpuQ3P2tM+nh65Bu9Q92jD3jpNukMTtRUE89O50vvz+DZFy381AW2Tf/UQZ/5i1E+0/jMavAw3J+lnqSbdRYiMLrlBCLRd9RhjFcXSlLQnHCup1pEZ7syGWVFHW6CGfc9K8IYsNqldgo713TarY9IUC1E9xY5z9rYMCxdZT4cl7bKa7IFvsp7Yavriv9skYaqgL7uCuuKZ1ShnNUCLvnpY2Paaer26o93oFUYwRMW2m3BQIVo+XH0sSFB2QzE3d/MGBU6tHFyOWmwJFkRYWRakgvkIj5sXfDw==
Received: from MWHPR19MB0957.namprd19.prod.outlook.com (2603:10b6:300:a4::16) by CO6PR19MB4769.namprd19.prod.outlook.com (2603:10b6:5:34d::6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19; Mon, 23 Aug 2021 23:30:34 +0000
Received: from MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783]) by MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783%4]) with mapi id 15.20.4436.024; Mon, 23 Aug 2021 23:30:33 +0000
From: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
To: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
Thread-Topic: [scim] SCIM Synchronization Problem
Thread-Index: AQHXlD4yOJYx7decRU+u2K9sFyDQQ6t7GC/QgAFl1QCABT8JsA==
Date: Mon, 23 Aug 2021 23:30:33 +0000
Message-ID: <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net>
In-Reply-To: <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: pdmconsulting.net; dkim=none (message not signed) header.d=none;pdmconsulting.net; dmarc=none action=none header.from=oneidentity.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 912e49dd-b1f6-4ed8-0553-08d9668e010d
x-ms-traffictypediagnostic: CO6PR19MB4769:
x-microsoft-antispam-prvs: <CO6PR19MB47696A15D76C0A34DEB4387DE1C49@CO6PR19MB4769.namprd19.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:3383;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: QaARE0owGIA63LkZPiRQNVTWXT5hDCtAHhQq2H8cxzE1naw8+UdM8Zx5td6B27sgKCQuV44xOxopUYfZs/PdGWWDArebtp1DNTlrvrsbmLNkhFKtr5i+eHEQ4IQjXLV0665bWAzifyJqQj/EzF4Bc1b7zIL0THhk98Xvx9f7KYTy1HIhV02Sgaw8wKxDr1x8vVSRB3I6Q6rqujyLEc4xIPOAskVamgJnbY+YXdZrrPR6UhWMoYahH/Mz78OMteRZAsMhoDYRvqfUCkOGugDBzkTyZGGlabJKnW8ySZeKrQzVQb4E8Kbsv1w87MKg39sZWXr29iMRzZa1to1OvTGBO9hHC4D/DHoBpJtfcIttVagr9lwmRpbG7jdFPWW7F1RqpiyUh9Dih4+/eV/a0vdq8bR7sVLcO4CSkBhb1ZpUXZSmpbdZOlLCd7LH7wZPZRpWP3Lwdgrf5MgHujoe7g7NhEGSp0VuxhRd4c7NHXJWg+8X61byEcQB6EO+wN47qTERIk0YPksIU5svHpsrrgMRjP6A+8nsUlJlMp38wSCcFgKnso2uSRyQ72XQhnWH6tAUf2sThDeWBi2BoBf7wr68HFEjwimauMTMXN+MJ0euJsBhS/jefgOg5/YxQ1kbFsqmSyxfPr2IXuM32UPgXCsYbDmtqE8Udr1zHFgb3rBb0NNWAS6tFAPXQXv4Sb/QHKsTlogXBkDh4WZam4/ueNiN4S+5kMmluvNQ8VubZAZGmFfPavXEUhG2Xf+KhVMqOIINUbJd/eukusFXdPU00Eqf0K3572GQCCMFBQr3EzbTv8Y=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MWHPR19MB0957.namprd19.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(52536014)(26005)(5660300002)(55236004)(186003)(53546011)(508600001)(6506007)(966005)(2906002)(83380400001)(86362001)(7696005)(110136005)(33656002)(45080400002)(9686003)(55016002)(71200400001)(38070700005)(122000001)(38100700002)(76116006)(66946007)(64756008)(66476007)(66446008)(66556008)(316002)(8936002)(8676002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?B+0xq8OX4l3efs8itl3mA+pntS8eMT499zUCuu7OYB/Yh8AF3X7Lmw4SnEAD?= =?us-ascii?Q?/OS8En1RuAbCTtazNl5edGMsM5uDjLL++j+ZKQKIq22lnzoLkaofalsyMnEK?= =?us-ascii?Q?OWRe9jEP1JmyX4UjT7GhNfi0lBH929f+jJwm4T1l/hbi/1hKoutGpEgPni3/?= =?us-ascii?Q?tJOLPUhIXHkd4Fp3vKtZ8/3L0/Lm4Tmrf0zDVuVuDWe8Lq95JCC4qIzPSRO0?= =?us-ascii?Q?Pf9zHIG9OMp33Y8DjKzFkq3td+ZCzdlngr6ZD4ekYqO+3qwdpardKxnmtt26?= =?us-ascii?Q?E02R73X4SLO32sJy+hToeeOI969+h1DoqR+Me8r1OAwwTP6bMYqAChH812Qt?= =?us-ascii?Q?1VqZ4h4zOBqvnuy8ddDvHjDUi3/ui7z8kWs7gwhyGRlnr1ikh09PJfUFUxPK?= =?us-ascii?Q?dPDM4re4y6zygIxgxf5XsoUs7dn2O4rniXO37Fr6+9cQz3S/J2PIXnL0Mib8?= =?us-ascii?Q?w7DxcwmCcBJ9uHmCJ5+3nXfBTCSt5MHwMdRoABBL1LOyn4tHgWk0CKH324ha?= =?us-ascii?Q?PdjQiVQTfL8Z0Jw8+W1Mg5TKvGdEnJFosrpv+QxYSw5owKjrXDVh+Bp0dlPj?= =?us-ascii?Q?drmCjHs1oaAibJ3roDKFHTztRwuQPFFymNInigXVqku0m2J4UxLDS4yITawl?= =?us-ascii?Q?2/4LNeGBUP7p5AIPOQovq1FIx0DnEFKW2+JKukUPNyDFR+HkrRjMPPLDeefc?= =?us-ascii?Q?X0GS/sk2O9JPeBKJ87UEC3Z/AzgzcLbACOY5vd2DaFr4eTqtTayIytSa5W9Z?= =?us-ascii?Q?/Zb4v5ndBzCtGXlkoOZGz9yiUrYwlYTtlmIgIG43wlw0Tu5B6d40Bs/sCzzN?= =?us-ascii?Q?TIKV3dXkOiWjfU6aQKUVoCElfOqz+sf+HscuVyApd4aqJ+694iLWE6Uy39dI?= =?us-ascii?Q?JxABF17/rdH+qDB4BcrzYG1P5Xj4onSJmibMYQGQkb/MCfTFFIPnkcEYlvg0?= =?us-ascii?Q?xQw9lljP0zxwmdrfswRAm+wgqiQNIhGel7LC6lVltZplP8ZK+xKcG85/BnBb?= =?us-ascii?Q?Y41gc8GmuY+puvuSr5xhtkFg9jkloT5D2ijD8y4izVhDOjG8uuzL1fg/WKsT?= =?us-ascii?Q?srCCBqsOo04mqJPhNYBjLBvYwoBnNrvLP0aRLpS9v3DOaswLZiBpU98SOxiU?= =?us-ascii?Q?8voJCQrNpm3tn6WWtmSZWvNZgI8p6mPlI5eyIm/LCDlrOBvqwe1e2Hr6q6FQ?= =?us-ascii?Q?hpLspAvHQkPsLWHwbIxJh9mufWU9cAS1kl7DahGOuq8kIeyOkYECuVOQxA7O?= =?us-ascii?Q?polvjYTXj1/vnFmcumkyZUd8SMMg3Q5G3n2G3GjDb1219oSygGHFe7E51Dst?= =?us-ascii?Q?rs3kpJmmqHEQAdJYjB7o3bZx?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: oneidentity.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR19MB0957.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 912e49dd-b1f6-4ed8-0553-08d9668e010d
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2021 23:30:33.7156 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 91c369b5-1c9e-439c-989c-1867ec606603
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: fOir9jwdgIfrDh2UT8CbRDV8m/JlXgEmmpDgZUwaxDffPSO3WzXGRWPdGs5BFp5QDoJnWM1Y3lDMFulLcXqnnA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO6PR19MB4769
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/_66fD-5Zjv2PGXTD522icY4vH_M>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 23 Aug 2021 23:30:47 -0000

Thanks for the clarification. =20

"Client" and "Server" are as used dozens of times in the existing RFCs whic=
h makes these as useful in understanding the SCIM protocol as they are for =
understanding the HTTP protocol.  In a SCIM protocol exchange there is a th=
ing that provides a resource (the server) and a thing that makes a HTTP req=
uest (GET,POST,PUT,PATCH,DELETE) on the resource (the client). =20

I think it would be helpful to try and use this generally accepted HTTP ter=
minology if we can -- especially when talking about this synchronization to=
pic. =20

Management server <-- SCIM Client
Application Server <-- SCIM Server

With this clarification, seems to me like your Management Server is using S=
CIM to manage accounts on the Application Server, and that the Management S=
erver would benefit from having an up-to-date cache of accounts that are on=
 the Application Server(s) even for cases where account changes/additions/d=
eletions are made "out of band"  (e.g. directly on the Application Server, =
not initiated by the Management server.)

Did I understand correctly?



-----Original Message-----
From: Danny Mayer <mayer@pdmconsulting.net>=20
Sent: Friday, August 20, 2021 8:54 AM
To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <scim=
@ietf.org>
Subject: Re: [scim] SCIM Synchronization Problem

CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.


I decided to avoid the client/server naming convention because I find it co=
nfusing. The system responsible for managing the user accounts and groups I=
 have declared to be the Management server. I believe you describe this as =
the "SCIM Client" and is used to GET/POST/PATCH, etc.
to the Application server to maintain the user accounts and groups. The app=
lication server is what I believe you call the "SCIM Server". This provides=
 the SCIM API's needed.

I find the use of client/server not helpful to understand their role in the=
 protocol.

Danny

On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
> Danny,
>
> To help me understand in your post is the "SCIM Client" and what is the "=
SCIM Server" can you tell me which of your components (the Management Serve=
r or the Application Server) implements SCIM endpoints?
>
> The component that acts as a "SCIM Server" is the component that provides=
 the of WebAPI endpoints that conform to the SCIM spec.  For example, the  =
/user, /group SCIM endpoints.
>
> The component(s) that uses these endpoints to query (GET)  users/groups o=
r to create (POST) user/groups is the "SCIM client".
>
> --
> Matt
>
> -----Original Message-----
> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> Sent: Wednesday, August 18, 2021 8:34 AM
> To: SCIM WG <scim@ietf.org>
> Subject: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not f=
ollow guidance, click links, or open attachments unless you recognize the s=
ender and know the content is safe.
>
>
> I decided that this needs it's own thread and not be part of the meeting =
minutes.
>
> I have had a great deal of experience dealing with the user account synch=
ronization problem. Here's my view of the problems.
>
> I will be calling one system Management Server and the other system Appli=
cation Server. I found client/server labels confusing. The Management Serve=
r is what I am defining to be the server that sends updates to add/update/r=
emove users and groups to the Application server whose account, groups and =
access permissions are being managed.
>
> First some definitions of user accounts. There are usually more than one =
of each of these:
> 1. Builtin accounts
> 2. Special-purpose accounts
> 3. Employee
> 4. Contractor
> 5. Agent
> 6. Customer
>
> There may be more.
>
> 1. Builtin accounts: These are accounts that applications have and there =
may be more than one. There is always an admin account which can do anythin=
g, for example the administrator account in Active Directory or a database =
admin account. The application may have more accounts for other purposes.
>
> 2. Special-purpose accounts: These may be set up to provide access to oth=
er applications, for example a SCIM request to a SCIM REST API should be ha=
ndled by a special account which cannot be used to login via a UI interface=
 and only be able to perform certain functions. In addition there may be ac=
counts set up to listen for topics or queues on a message queue among other=
 possibilities. Keeping separate accounts like this are important for track=
ing in logs and applications.
>
> 3. Employee: These are accounts that employees may login to the applicati=
on.
>
> 4. Contractors: These accounts that a contractor performing work for the =
company may use to log into an application. Unlike Employee accounts these =
would have an expiration date.
>
> 5. Agent: Accounts like this are for external users who may need to manag=
e information for their own customers. An example of this is an insurance a=
gent logging in to handle an insurance policy for their clients.
>
> 6. Customers: These are where the customers are using the application dir=
ectly. For a bank it's likely to be millions of customers. The management p=
latform should not be involved in managing these accounts.
>
> Let's now look at a few example applications.
>
> 1. Helpdesk
> All employees and contractors will need to be able to log into a helpdesk=
 application and enter tickets. This means loading information about all em=
ployees and contractors. For a company with only 1000 employees that's mana=
geable. For a company with 100K employees, it's a bigger challenge.
>
> 2. Customer Support
> Only employees or contractors in the department providing customer suppor=
t need access plus a few other employees. In addition identified customers =
may need accounts.
>
> 3. Expenses
> Not all employees or contractors will be submitting expenses so it may no=
t be necessary to have accounts for all possible users. This is something t=
hat the application owner needs to decide.
>
> Now let's look at logistics.
>
> Bulk load:
> Each application will need an initial set of accounts set up and for some=
thing like a helpdesk this could involve load 1000-100,000 accounts.
> The information needed could come from either the management server or se=
parately, say from an HR system. Many servers that I have encountered limit=
 the number of records to something like 1000, so the pagination requiremen=
t is needed for this. Even when dealing with a limited subset of employees =
or contractors you can run into this need.
>
> Synchronization
> An application that is bulk-loaded above may need to be synchronized to t=
he management server if the data did not come from the management server.
>
> Change Management
> This is really a synchronization issue as well. Changes happen all the ti=
me and new employees/contractors need to be added, terminated ones removed =
and updates happen all the time. The best way of dealing with this may be t=
o set up a message queue that each application can subscribe to and they ca=
n take the needed action when it's convenient for that application. It's no=
t the only method but it's the one I found to be the most helpful. There ar=
e two ways of doing that: 1. send the complete user information for new acc=
ounts, send just the change for updating accounts, send the ID for terminat=
ed accounts along with some meta information. The other method which I have=
 used is just to send the ID and whether it's new, updated or terminated.
>
> I hope this is helpful to the discussion.
>
> Danny
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7CMatt.Peterson%
> 40oneidentity.com%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439
> c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d
> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> 3000&amp;sdata=3DBqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;
> reserved=3D0
>


From nobody Mon Aug 23 16:50:05 2021
Return-Path: <Matt.Peterson@oneidentity.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 9C01E3A0B3E for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 16:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level: 
X-Spam-Status: No, score=-2.091 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oneidentity.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 3t9JJt7jzIhj for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 16:49:34 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1anam02on2123.outbound.protection.outlook.com [40.107.96.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC0DD3A0B46 for <scim@ietf.org>; Mon, 23 Aug 2021 16:49:33 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Q384XsELfPJNJXf+IPE3RcpzMOEkUvy2DA4HNM86olKDwVvnmbdVDAF+LtniB1GCbdXrgnNuwnKbs48eppxGQTi1lM3KA3PM2Sc/0woq+/DxF3OES8T3eVqTZA+Co+DKt4mwnLRlnv+zVzAFZmhuERycEfMUo/QoHygT708Vl58rZwJwvHTliJ8MFhaF2+gpxbYPCb8IfqJ6f753lzGFR3CajJgFTULTnMARHKEv/KFRIZXM21K0K/4XOmPSS9JK7DVd11jRj8077QyeoVYn6mTqlMv6v9E/Gfk4aM6toM0UK48w4HNUpmmrx94JqhTvdRdKWspIeADnG7WcBIE6Rg==
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=/m4ZtXp8l2NnFn0O/q9WG1cWIhO6mLwe6O4jXeBAH7A=; b=C+yeK6dHWbHxFtWaSuJ/nt1G25vtLbvaphKKaniWke/qMleCQDYunZ8UFb58MMgz1AlR3zo5kCv7Ft9jH9FZ6cAtKsPnpIibHXqNDz7biTEIm97v/vvdGgCXaoJGMavT1yALI/hM6WA9MiJ5X4MjioiuTZOpW9xVneolFBN5ctkMddcEXdE7W+PMV6B/HsEK3uwyEXQZA0AyenCzssUlyJJCDv21WH2VmOj+FnXHK2TfUQHdOOiyq1NFkioJe3iFAnB/xptggxNiwZza5ZyazeyrAqaYV/GaupH1rGyYgO77UjfiYskGe3Nyc5xXZhvzZcRKERzZqDFEo1pdOlpPLg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oneidentity.com; dmarc=pass action=none header.from=oneidentity.com; dkim=pass header.d=oneidentity.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oneidentity.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/m4ZtXp8l2NnFn0O/q9WG1cWIhO6mLwe6O4jXeBAH7A=; b=AkOIBL9+1IIYame7x0McpVsmSRx8fqPfP2qrqvAQaxKzFx3hnKcOr0ggjPWNA6K1aIGSQ96iTs/bb5P4kH3Y6Kl0aqP2zMSA8iXamiWxJQwY+BimoNlIlMNl65PiyTudagyvb3aA51RJwO8R7bfRjfaIYmbj6mdOJ/nbtxNHd2ToRxLkj3Y44Qjy3Mxn/uZPkVp42dtYhdlin+ddZAiMYIuZ+urxn7et315rnhrcPNDgA8JrUoqCLQPVNG5HEhGUsJOU3860bBCM0yJNi6587gneHjuYk7pfqUSGTaTfEoBK+Yh5RfjeHVR+UgrHxumsmb/RIYPt3jU1m7zfb7Wtqg==
Received: from MWHPR19MB0957.namprd19.prod.outlook.com (2603:10b6:300:a4::16) by CO6PR19MB4755.namprd19.prod.outlook.com (2603:10b6:5:341::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4436.19; Mon, 23 Aug 2021 23:49:22 +0000
Received: from MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783]) by MWHPR19MB0957.namprd19.prod.outlook.com ([fe80::4880:4967:c535:5783%4]) with mapi id 15.20.4436.024; Mon, 23 Aug 2021 23:49:22 +0000
From: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>
To: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
Thread-Topic: [scim] SCIM Synchronization Problem
Thread-Index: AQHXlD4yOJYx7decRU+u2K9sFyDQQ6t7FibQgAFlnoCABUmcsA==
Date: Mon, 23 Aug 2021 23:49:22 +0000
Message-ID: <MWHPR19MB0957723BC8FE476F68EBDEC6E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <0f21255e-4ea9-b42d-353d-5c0661e1be5e@pdmconsulting.net>
In-Reply-To: <0f21255e-4ea9-b42d-353d-5c0661e1be5e@pdmconsulting.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: pdmconsulting.net; dkim=none (message not signed) header.d=none;pdmconsulting.net; dmarc=none action=none header.from=oneidentity.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f14663bb-5a9b-4ca7-79c8-08d96690a1b6
x-ms-traffictypediagnostic: CO6PR19MB4755:
x-microsoft-antispam-prvs: <CO6PR19MB4755B80B39E91FFA42D31C88E1C49@CO6PR19MB4755.namprd19.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FG0i7ZI6Y01lO96r8mU8hsJpE4TU2PzCo6gr8KHZEJmh9KLYFWgX1YJ5PXAA8zILkcDQHCIJ/Mop3XM5Y/+SE1y6dQX/oYFwc5qS7Zs/G5xYygXkWe1k4leMsNWnfx0QYCkWdTmcrCx/Bl3ErdkKVV7Ypda18eVg5NqPXJ3yyW2cWdutgaExm8D1ifJC1oxqth1O0dUmvODd53s3Ax89WdH8K3nB0hyg1QVDVlfU5B8Nh6lJhLSWIk+EKFwPdNWJv2cxAQ3LFjQlqo1BSwQrdW0/QSJ21PT1ftYEcX3Fzg6ItXD1Igcd3v58QpS9Ay9NUOQHY/Ay2tblYvF1yuB+PsYwWpB8S5BDzoyiU7atBhDMx28UnXMpjM1DQMF2L8dQpVgKJv7Ac4RHxcMBuyt5MgOta3C2hiCAFfsNAns2KKiiXrrFr0hnyI8vBKGZsg0STE+HiMMpuK2A0rhiv8zmdOaCUpFdBzd2n6CcBnat8DBGuqHzfNQcodYImqwwSf12b1mtCRbWChcDlNDw8jSYKnUh7FCjAdfH9lzknKvKld8zONJQXgE8465qaRG70nnGPfNfg/TretfUQRz37jOhUhBehPmdZQKOueV3ELkFYFjRC/xKGdJWkJQKxQDA4bejlvdI8CUuuA00QVFtnD/VSn3xBvWjt5035nl0gfKXmr0Pisg1FsRv9344Q5oKrUIFD7fwbPaLR8P32snNzud3440WYcJel7oNaBT8oKOEqANdxgZIOMjNzcZPU0WTjpob4/cQlleqZH02KcgCoNukyJGD1nTTS5jmiJWQD+gGGew=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MWHPR19MB0957.namprd19.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(136003)(366004)(396003)(376002)(39860400002)(76116006)(66446008)(66556008)(64756008)(66476007)(38100700002)(66946007)(122000001)(8936002)(8676002)(316002)(86362001)(83380400001)(2906002)(33656002)(7696005)(110136005)(26005)(52536014)(6506007)(186003)(53546011)(5660300002)(55236004)(966005)(71200400001)(55016002)(45080400002)(9686003)(478600001)(38070700005); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?2EKXtFM8apSP5QTEsHmFWO4gec37h4/X4vCDh/HPHuuECVn2LZ9WrejZP8Qr?= =?us-ascii?Q?ixzjrOP7IPakK5oksWOKs/m23SvyCV660kcE0KKMS/XpZexyWnBPGTT8u1uR?= =?us-ascii?Q?mh0+U+bQpzXnYc5sRCAVDbA7goHIsrN8gKIzmQLpnvKh9syb8ORO32NgCXjt?= =?us-ascii?Q?kp7Hq79mx+4FH1h/V9ktjqaDof3ujtcvPBW1l8AN3uL9LLC0pNPdAXUEsAVi?= =?us-ascii?Q?R4XE4Dj31ya5fjfMFuw0GCi2uMsHgIw7XIvUY/pc8TYVXa1nVmEYmMqHPOAa?= =?us-ascii?Q?B1YUbkeT4gM2cLbMiEZ8QtdoZAOvYUKZmAA78POxz6F0qWMt9u0IPtyzHZq9?= =?us-ascii?Q?2RICfhKzVWaOKHvDZZsj+v/twNIrR4oz4hb1GbriTAcxqeh2mmuwMEmNEfUP?= =?us-ascii?Q?xbcGQFsRVvAvVtGQT++BrF4ZHrez7cUcbeN6rdX5k+Bp9//L7e/xpqMX6fhP?= =?us-ascii?Q?78eSJTsDXa65A3aI8FRV/NhV8Un1l3FsiAmcUeX1NU9iXX/MK6vVhHiXdssw?= =?us-ascii?Q?3diUtZ6O5I9CFVhG1du/cOlP/HjpCYMgHIxke1xYFbE2SLUkvsw0cYy3cxqJ?= =?us-ascii?Q?ywwUfoVpzpzCOYIXVNlfzDX88mgk0dHX5yKbT8yQS5LsDB784yN8Mwhlkmqw?= =?us-ascii?Q?JFWX123la0/SV9e2Gr65SKfTTAwgoxtmWzJcAOz7qd98z2NUNibJatVWffeZ?= =?us-ascii?Q?Q5L55pMEsRuLoJwe+Muf81YF95K4L1JvAt0amUy4CSkaI2pgq1HuCWJM09xo?= =?us-ascii?Q?hR0axZoc+90XgWa8dkQQV2ZUeNPaQvQg9/2b+shG9b5ixvIWyv2YrQPxupY+?= =?us-ascii?Q?JfcBsvIm/rwHBSV+VSzl3vzk8OehGKHLrt8FxfCiDGGMWdnLpCWRPrRz6Bq0?= =?us-ascii?Q?HndhSHFlSgEfEearCDUEhZYBiwdeIkQNzPlS73bxYm56o34Hezf5Pf3jIRe4?= =?us-ascii?Q?Uv09rrhg72eUfjEmu75oHUea1afurRwtYMEUItUz1hI5UtGxWuhwlI6jdn7D?= =?us-ascii?Q?2v86fkFKkUdjBT29BDZlMjz8lBkY5l4U5zwat0/MJZE0D/s1QI0IzmEyjvdF?= =?us-ascii?Q?BeGnOpd0JXnNLXkP5Pj8lbUBjLEbvVkOTTzlDzPxh7aC/O8sdFHmRcaUrLez?= =?us-ascii?Q?33Pri9E7Kl5EcltmV3IT7pje57pgQhv7PzTotmXsOShtKbXiof4vesWQ3BVl?= =?us-ascii?Q?fQfSyqsQOAE8/GfBrXR2hiUGMxaniUTZ7Q3Qc+ek1UnFFM9ntZKN5Q0fGLqs?= =?us-ascii?Q?OmxElLIZg96uOng3XIIq7+WcFEcwYNCnSvGNZvWZTQFkaVLt09ODnnnkbL21?= =?us-ascii?Q?IQXDQZlVDlxmuVnlTFq0JnkC?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: oneidentity.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR19MB0957.namprd19.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f14663bb-5a9b-4ca7-79c8-08d96690a1b6
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Aug 2021 23:49:22.3250 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 91c369b5-1c9e-439c-989c-1867ec606603
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yuXkbnovOYu/BvHHaYE25VPg2pl2UUWZQ//95TyCtHctDv/Ha+aucJ5JwOLOoh6T7+p2qWcH4PpdfS84ljqHow==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO6PR19MB4755
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/7gNtfKSIBMmjt4G1SFXxIYs-ssc>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 23 Aug 2021 23:49:52 -0000

The management server in your scenario is a SCIM client. =20

If an application administrator goes in to the Application Server  and adds=
, removes, or modifies account,  the Management Server  has one option when=
 using SCIM -- which is to query the Application Server (the SCIM server) f=
or all accounts and then resolve the differences between this call and a pr=
evious call where all accounts were fetched.   This is very inefficient.  E=
specially when it comes to detecting deleted accounts, there is no other wa=
y in standard SCIM except to have your Management Server re-load all the ac=
counts from your Application server. =20

What you've implemented in your Management Server *is* a pure client-side c=
ache scenario as I described it.  Except that you've recognized that the SC=
IM spec makes it very inefficient to keep your Management Serve up-to-date =
with changes happening "out-of-band" on the Application Servers. =20

So... you implemented a notification system whereby your Management Server =
(SCIM Client) can be notified of changes that just happened on the Applicat=
ion Server (the SCIM server).
=20
Your implementation, where the Application Server (SCIM server) notifies yo=
ur Management Server (SCIM client) that a change has occurred *is* one of t=
he proposed technical approaches identified by @Phil in a previous post to =
this list and was also mentioned in the BOF. =20

I believe that an approach (similar to your implementation ) whereby a SCIM=
 client can subscribe to be notified of changes on the SCIM server is an in=
tuitive approach for solving the "Syncronization problem"

--
Matt


-----Original Message-----
From: Danny Mayer <mayer@pdmconsulting.net>=20
Sent: Friday, August 20, 2021 8:46 AM
To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <scim=
@ietf.org>
Subject: Re: [scim] SCIM Synchronization Problem

CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.


It's not that simple. If an administrator goes in an adds a new account or =
updates an existing account and adds permissions to it, how will the manage=
ment side know? The way I did it was to have the application monitor for th=
ose changes and notify the management server of the changes. I did this via=
 a message queue for our internal applications.
The management server needs to decide how to handle these violations.

Danny

On 8/19/21 1:33 PM, Matt Peterson (mpeterso) wrote:
> Thank you, Danny, for creating a new thread.  The following are my commen=
ts from meeting minutes (some edits):
>
> There appears to be two use cases for "synchronization":
>
>    1.  Constructing and enforcing Application authorization models -  An =
application (acting as a SCIM client) caches users/groups data from the IdP=
 in order to present "user/group pickers" when presenting screens used to c=
onfigure the application  authorization rules (RBAC, Policy, or ACL).  Also=
, when the application enforces authorization, user and group data needs to=
 be immediately available so that authorization decisions can be made quick=
ly.
>
>    2.  Identity Management and Governance systems - implement a canonical=
 identity model" where all accounts and groups are represented.  This model=
 is used to build provisioning rules and calculate separation of duty viola=
tions, attestations, and approvals etc.   Management-time evaluation of the=
 model needs to be done efficiently without external calls to the SCIM serv=
ice provider.
>
> Both above use cases, are "client-cache" use cases that need only a "one-=
way" sync (from the SCIM server to the SCIM client).   To accomplish there =
are two distinct steps:  a) download the initial results (users/groups) and=
, b) keep the cached copy of these initial results (user/groups) up to date=
 with changes that are being made on the SCIM Service provider.
>
> I think it could help us narrow down the list of suitable approaches if w=
e could agree that "one-way" sync (keeping a client-side cache up to date) =
is our target.
>
> --
> Matt Peterson
>
> -----Original Message-----
> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> Sent: Wednesday, August 18, 2021 8:34 AM
> To: SCIM WG <scim@ietf.org>
> Subject: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not f=
ollow guidance, click links, or open attachments unless you recognize the s=
ender and know the content is safe.
>
>
> I decided that this needs it's own thread and not be part of the meeting =
minutes.
>
> I have had a great deal of experience dealing with the user account synch=
ronization problem. Here's my view of the problems.
>
> I will be calling one system Management Server and the other system Appli=
cation Server. I found client/server labels confusing. The Management Serve=
r is what I am defining to be the server that sends updates to add/update/r=
emove users and groups to the Application server whose account, groups and =
access permissions are being managed.
>
> First some definitions of user accounts. There are usually more than one =
of each of these:
> 1. Builtin accounts
> 2. Special-purpose accounts
> 3. Employee
> 4. Contractor
> 5. Agent
> 6. Customer
>
> There may be more.
>
> 1. Builtin accounts: These are accounts that applications have and there =
may be more than one. There is always an admin account which can do anythin=
g, for example the administrator account in Active Directory or a database =
admin account. The application may have more accounts for other purposes.
>
> 2. Special-purpose accounts: These may be set up to provide access to oth=
er applications, for example a SCIM request to a SCIM REST API should be ha=
ndled by a special account which cannot be used to login via a UI interface=
 and only be able to perform certain functions. In addition there may be ac=
counts set up to listen for topics or queues on a message queue among other=
 possibilities. Keeping separate accounts like this are important for track=
ing in logs and applications.
>
> 3. Employee: These are accounts that employees may login to the applicati=
on.
>
> 4. Contractors: These accounts that a contractor performing work for the =
company may use to log into an application. Unlike Employee accounts these =
would have an expiration date.
>
> 5. Agent: Accounts like this are for external users who may need to manag=
e information for their own customers. An example of this is an insurance a=
gent logging in to handle an insurance policy for their clients.
>
> 6. Customers: These are where the customers are using the application dir=
ectly. For a bank it's likely to be millions of customers. The management p=
latform should not be involved in managing these accounts.
>
> Let's now look at a few example applications.
>
> 1. Helpdesk
> All employees and contractors will need to be able to log into a helpdesk=
 application and enter tickets. This means loading information about all em=
ployees and contractors. For a company with only 1000 employees that's mana=
geable. For a company with 100K employees, it's a bigger challenge.
>
> 2. Customer Support
> Only employees or contractors in the department providing customer suppor=
t need access plus a few other employees. In addition identified customers =
may need accounts.
>
> 3. Expenses
> Not all employees or contractors will be submitting expenses so it may no=
t be necessary to have accounts for all possible users. This is something t=
hat the application owner needs to decide.
>
> Now let's look at logistics.
>
> Bulk load:
> Each application will need an initial set of accounts set up and for some=
thing like a helpdesk this could involve load 1000-100,000 accounts.
> The information needed could come from either the management server or se=
parately, say from an HR system. Many servers that I have encountered limit=
 the number of records to something like 1000, so the pagination requiremen=
t is needed for this. Even when dealing with a limited subset of employees =
or contractors you can run into this need.
>
> Synchronization
> An application that is bulk-loaded above may need to be synchronized to t=
he management server if the data did not come from the management server.
>
> Change Management
> This is really a synchronization issue as well. Changes happen all the ti=
me and new employees/contractors need to be added, terminated ones removed =
and updates happen all the time. The best way of dealing with this may be t=
o set up a message queue that each application can subscribe to and they ca=
n take the needed action when it's convenient for that application. It's no=
t the only method but it's the one I found to be the most helpful. There ar=
e two ways of doing that: 1. send the complete user information for new acc=
ounts, send just the change for updating accounts, send the ID for terminat=
ed accounts along with some meta information. The other method which I have=
 used is just to send the ID and whether it's new, updated or terminated.
>
> I hope this is helpful to the discussion.
>
> Danny
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7CMatt.Peterson%4=
0oneidentity.com%7C0502a1bbffb94f6220b808d963e944e9%7C91c369b51c9e439c989c1=
867ec606603%7C0%7C1%7C637650675822236228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC=
4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=
=3Dol7Mrjj%2Bx2SGTgQegrvwVNlVeMODf6pxEOc5PTjkK1g%3D&amp;reserved=3D0
>


From nobody Mon Aug 23 18:03:23 2021
Return-Path: <phil.hunt@independentid.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 2F49E3A11F4 for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 18:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 I1Hyg4JaM9Fq for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 18:03:14 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 9EF793A11F0 for <scim@ietf.org>; Mon, 23 Aug 2021 18:03:14 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id m17so4180290plc.6 for <scim@ietf.org>; Mon, 23 Aug 2021 18:03:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=r+issObLs72AXyNLcviIwf4mNPI4ynlyrT/uE47T5zU=; b=FIVFQ0Q1Mmu+t6wupCp9epURHiU3GxAQ50iYbRpRNZbhPAhKE43YgZP3gerVHeqySN frDDklA4XN4kxOer9oZnQt2Uiebq6ydHCm8Eq4JMzM/qTco8MJAhHg0+aTUNdRb7V48m 0WgnweMj9DJRibsszeE7c8zW8LrtfoOroT6V2HXnQkfq0KtzCJYnGFkOC7CzecIrdW27 r4TCPsCA+pR02BLqdxYIRpjoLVQKn6pVU5o3EemRmpqjGHj0at+2VlchRJ3NM/DqH44q 2Utls4TwKjc1KNO9S1oLM37iQbe/kgOLTQNXxO3NOsqYrNNetc/jqQqVyjDhNS3btdkL 24zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=r+issObLs72AXyNLcviIwf4mNPI4ynlyrT/uE47T5zU=; b=IhJ3ad+yh877DG3Q3Pyb8MeKj1E9w/u1Nr/kHksHwOu8FCAd+6c0evmpmpQhzRLAzq RdVlzmHoPDEU07yM/qk18uzSJrHsrAP0mfqvShlYEpMnAu3NH7hMAexgpI4StanncZTR Ckoe+2/UTkZngVHEXktOQM3ZAhlcBBgPz6zlRQ8gphtb4X0wTdVeHErc2y0n+sDc46kb iXjENXXjqjS3MLjRym1/jkqvgldXC8VvbR5oUhJqdwNgRNn0/L8gvGT4NrBMhEZvxfM/ cH1Ef/iWGf4E+FESLwYwDc0kMjfkkLX/T1YD9iZte289ImQDFA6aFofZmYQWhxSkaKEn YmmQ==
X-Gm-Message-State: AOAM53096EqUSSpl3IR6dFQptoByHKsddCcCU63c8tLj2LGg2NBGriBX Hre3mMTpdqenBhXx0u/6riaX2jMUxwjh2esg
X-Google-Smtp-Source: ABdhPJxb1Gzdmy6jcolJR5mRb1b6uWnUeNYf5sAiDoB8nREa9L8rWNVRZR6R5RZIJ00wGuuOhWFx2A==
X-Received: by 2002:a17:903:18f:b0:130:2a02:1c9a with SMTP id z15-20020a170903018f00b001302a021c9amr19926984plg.78.1629766993384;  Mon, 23 Aug 2021 18:03:13 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9qrfoxx7wvwgxp6p1ofw.ipv6.telus.net. [2001:569:7a71:1d00:1991:85db:82f0:92fc]) by smtp.gmail.com with ESMTPSA id t15sm15189676pgk.13.2021.08.23.18.03.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Aug 2021 18:03:12 -0700 (PDT)
From: Phil Hunt <phil.hunt@independentid.com>
Message-Id: <439E06DD-213B-4C53-8BB7-EFF91ACB2FE9@independentid.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_07A371A5-0D65-4142-818A-A90183AD8BE8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Mon, 23 Aug 2021 18:03:11 -0700
In-Reply-To: <MWHPR19MB0957723BC8FE476F68EBDEC6E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
Cc: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
To: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <0f21255e-4ea9-b42d-353d-5c0661e1be5e@pdmconsulting.net> <MWHPR19MB0957723BC8FE476F68EBDEC6E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/3Q-Wm0ib0DRRD2OpR8VxaehwOe0>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 01:03:22 -0000

--Apple-Mail=_07A371A5-0D65-4142-818A-A90183AD8BE8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1 Matt

Ironically when developing the Security Event Token spec, we listed a =
hypothetical SCIM example in RFC8417.  For example in Section 2.2.1 =
(https://datatracker.ietf.org/doc/html/rfc8417#section-2.1.1), a =
password reset event.

  {
     "iss": "https://scim.example.com",
     "iat": 1458496025,
     "jti": "3d0c3cf797584bd193bd0fb1bd4e7d30",
     "aud": [
       "https://jhub.example.com/Feeds/98d52461fa5bbc879593b7754",
       "https://jhub.example.com/Feeds/5d7604516b1d08641d7676ee7"
     ],
     "sub": "https://scim.example.com/Users/44f6142df96bd6ab61e7521d9",
     "events": {
       "urn:ietf:params:scim:event:passwordReset": {
         "id": "44f6142df96bd6ab61e7521d9"
       },
       "https://example.com/scim/event/passwordResetExt": {
         "resetAttempts": 5
       }
     }
   }

Notice under the =E2=80=9Cevents=E2=80=9D attribute is a somewhat SCIM =
like structure consisting of an Event ID =
(urn:ietf:params:scim:event:passwordReset), a payload (the id). The =
example has an extension where additional data is provided which in this =
case is =E2=80=9CresetAttempts=E2=80=9D.

We could also have a set of *simple* IDM events indicating:  CREATE, =
MODIFY, DELETE and an id.  The events don=E2=80=99t even have to contain =
data. You could then have the receiver simply do a GET on the resource =
allowing it to reconcile the current resource.  This enables access =
control restrictions to process and keeps event payloads simple in the =
event.

SET has two approved RFCs for exchanging events, namely SET PUSH =
(RFC8935) and POLLING (RFC8936). =20

Polling mode is great when a management server behind a firewall.  It =
can use HTTP LONG POLLING in order to receive events in real time. =
Polling is also good because you can theoretically re-use the same =
credential to pick up events.  Push on the other hand requires a =
credential be placed in the publishing side to POST to the event =
receiver.

Push ends up being preferred in situations where a single event =
publisher has many 1000s of subscribers (this was the downfall of =
pubsubhubub).  I think for most SCIM cases, we are looking at more equal =
relationships of publishers to subscribers.

Phil Hunt
@independentid
phil.hunt@independentid.com




> On Aug 23, 2021, at 4:49 PM, Matt Peterson (mpeterso) =
<Matt.Peterson=3D40oneidentity.com@dmarc.ietf.org> wrote:
>=20
> The management server in your scenario is a SCIM client. =20
>=20
> If an application administrator goes in to the Application Server  and =
adds, removes, or modifies account,  the Management Server  has one =
option when using SCIM -- which is to query the Application Server (the =
SCIM server) for all accounts and then resolve the differences between =
this call and a previous call where all accounts were fetched.   This is =
very inefficient.  Especially when it comes to detecting deleted =
accounts, there is no other way in standard SCIM except to have your =
Management Server re-load all the accounts from your Application server. =
=20
>=20
> What you've implemented in your Management Server *is* a pure =
client-side cache scenario as I described it.  Except that you've =
recognized that the SCIM spec makes it very inefficient to keep your =
Management Serve up-to-date with changes happening "out-of-band" on the =
Application Servers. =20
>=20
> So... you implemented a notification system whereby your Management =
Server (SCIM Client) can be notified of changes that just happened on =
the Application Server (the SCIM server).
>=20
> Your implementation, where the Application Server (SCIM server) =
notifies your Management Server (SCIM client) that a change has occurred =
*is* one of the proposed technical approaches identified by @Phil in a =
previous post to this list and was also mentioned in the BOF. =20
>=20
> I believe that an approach (similar to your implementation ) whereby a =
SCIM client can subscribe to be notified of changes on the SCIM server =
is an intuitive approach for solving the "Syncronization problem"
>=20
> --
> Matt
>=20
>=20
> -----Original Message-----
> From: Danny Mayer <mayer@pdmconsulting.net =
<mailto:mayer@pdmconsulting.net>>=20
> Sent: Friday, August 20, 2021 8:46 AM
> To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com =
<mailto:Matt.Peterson@oneidentity.com>>; SCIM WG <scim@ietf.org =
<mailto:scim@ietf.org>>
> Subject: Re: [scim] SCIM Synchronization Problem
>=20
> CAUTION: This email originated from outside of the organization. Do =
not follow guidance, click links, or open attachments unless you =
recognize the sender and know the content is safe.
>=20
>=20
> It's not that simple. If an administrator goes in an adds a new =
account or updates an existing account and adds permissions to it, how =
will the management side know? The way I did it was to have the =
application monitor for those changes and notify the management server =
of the changes. I did this via a message queue for our internal =
applications.
> The management server needs to decide how to handle these violations.
>=20
> Danny
>=20
> On 8/19/21 1:33 PM, Matt Peterson (mpeterso) wrote:
>> Thank you, Danny, for creating a new thread.  The following are my =
comments from meeting minutes (some edits):
>>=20
>> There appears to be two use cases for "synchronization":
>>=20
>>   1.  Constructing and enforcing Application authorization models -  =
An application (acting as a SCIM client) caches users/groups data from =
the IdP in order to present "user/group pickers" when presenting screens =
used to configure the application  authorization rules (RBAC, Policy, or =
ACL).  Also, when the application enforces authorization, user and group =
data needs to be immediately available so that authorization decisions =
can be made quickly.
>>=20
>>   2.  Identity Management and Governance systems - implement a =
canonical identity model" where all accounts and groups are represented. =
 This model is used to build provisioning rules and calculate separation =
of duty violations, attestations, and approvals etc.   Management-time =
evaluation of the model needs to be done efficiently without external =
calls to the SCIM service provider.
>>=20
>> Both above use cases, are "client-cache" use cases that need only a =
"one-way" sync (from the SCIM server to the SCIM client).   To =
accomplish there are two distinct steps:  a) download the initial =
results (users/groups) and, b) keep the cached copy of these initial =
results (user/groups) up to date with changes that are being made on the =
SCIM Service provider.
>>=20
>> I think it could help us narrow down the list of suitable approaches =
if we could agree that "one-way" sync (keeping a client-side cache up to =
date) is our target.
>>=20
>> --
>> Matt Peterson
>>=20
>> -----Original Message-----
>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>> Sent: Wednesday, August 18, 2021 8:34 AM
>> To: SCIM WG <scim@ietf.org>
>> Subject: [scim] SCIM Synchronization Problem
>>=20
>> CAUTION: This email originated from outside of the organization. Do =
not follow guidance, click links, or open attachments unless you =
recognize the sender and know the content is safe.
>>=20
>>=20
>> I decided that this needs it's own thread and not be part of the =
meeting minutes.
>>=20
>> I have had a great deal of experience dealing with the user account =
synchronization problem. Here's my view of the problems.
>>=20
>> I will be calling one system Management Server and the other system =
Application Server. I found client/server labels confusing. The =
Management Server is what I am defining to be the server that sends =
updates to add/update/remove users and groups to the Application server =
whose account, groups and access permissions are being managed.
>>=20
>> First some definitions of user accounts. There are usually more than =
one of each of these:
>> 1. Builtin accounts
>> 2. Special-purpose accounts
>> 3. Employee
>> 4. Contractor
>> 5. Agent
>> 6. Customer
>>=20
>> There may be more.
>>=20
>> 1. Builtin accounts: These are accounts that applications have and =
there may be more than one. There is always an admin account which can =
do anything, for example the administrator account in Active Directory =
or a database admin account. The application may have more accounts for =
other purposes.
>>=20
>> 2. Special-purpose accounts: These may be set up to provide access to =
other applications, for example a SCIM request to a SCIM REST API should =
be handled by a special account which cannot be used to login via a UI =
interface and only be able to perform certain functions. In addition =
there may be accounts set up to listen for topics or queues on a message =
queue among other possibilities. Keeping separate accounts like this are =
important for tracking in logs and applications.
>>=20
>> 3. Employee: These are accounts that employees may login to the =
application.
>>=20
>> 4. Contractors: These accounts that a contractor performing work for =
the company may use to log into an application. Unlike Employee accounts =
these would have an expiration date.
>>=20
>> 5. Agent: Accounts like this are for external users who may need to =
manage information for their own customers. An example of this is an =
insurance agent logging in to handle an insurance policy for their =
clients.
>>=20
>> 6. Customers: These are where the customers are using the application =
directly. For a bank it's likely to be millions of customers. The =
management platform should not be involved in managing these accounts.
>>=20
>> Let's now look at a few example applications.
>>=20
>> 1. Helpdesk
>> All employees and contractors will need to be able to log into a =
helpdesk application and enter tickets. This means loading information =
about all employees and contractors. For a company with only 1000 =
employees that's manageable. For a company with 100K employees, it's a =
bigger challenge.
>>=20
>> 2. Customer Support
>> Only employees or contractors in the department providing customer =
support need access plus a few other employees. In addition identified =
customers may need accounts.
>>=20
>> 3. Expenses
>> Not all employees or contractors will be submitting expenses so it =
may not be necessary to have accounts for all possible users. This is =
something that the application owner needs to decide.
>>=20
>> Now let's look at logistics.
>>=20
>> Bulk load:
>> Each application will need an initial set of accounts set up and for =
something like a helpdesk this could involve load 1000-100,000 accounts.
>> The information needed could come from either the management server =
or separately, say from an HR system. Many servers that I have =
encountered limit the number of records to something like 1000, so the =
pagination requirement is needed for this. Even when dealing with a =
limited subset of employees or contractors you can run into this need.
>>=20
>> Synchronization
>> An application that is bulk-loaded above may need to be synchronized =
to the management server if the data did not come from the management =
server.
>>=20
>> Change Management
>> This is really a synchronization issue as well. Changes happen all =
the time and new employees/contractors need to be added, terminated ones =
removed and updates happen all the time. The best way of dealing with =
this may be to set up a message queue that each application can =
subscribe to and they can take the needed action when it's convenient =
for that application. It's not the only method but it's the one I found =
to be the most helpful. There are two ways of doing that: 1. send the =
complete user information for new accounts, send just the change for =
updating accounts, send the ID for terminated accounts along with some =
meta information. The other method which I have used is just to send the =
ID and whether it's new, updated or terminated.
>>=20
>> I hope this is helpful to the discussion.
>>=20
>> Danny
>>=20
>>=20
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> =
https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.
>> ietf.org =
<http://ietf.org/>%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7CMatt.P=
eterson%40oneidentity.com =
<http://40oneidentity.com/>%7C0502a1bbffb94f6220b808d963e944e9%7C91c369b51=
c9e439c989c1867ec606603%7C0%7C1%7C637650675822236228%7CUnknown%7CTWFpbGZsb=
3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C30=
00&amp;sdata=3Dol7Mrjj%2Bx2SGTgQegrvwVNlVeMODf6pxEOc5PTjkK1g%3D&amp;reserv=
ed=3D0
>>=20
>=20
> _______________________________________________
> scim mailing list
> scim@ietf.org <mailto:scim@ietf.org>
> https://www.ietf.org/mailman/listinfo/scim =
<https://www.ietf.org/mailman/listinfo/scim>

--Apple-Mail=_07A371A5-0D65-4142-818A-A90183AD8BE8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">+1 =
Matt<div class=3D""><br class=3D""></div><div class=3D"">Ironically when =
developing the Security Event Token spec, we listed a hypothetical SCIM =
example in RFC8417. &nbsp;For example in Section 2.2.1 (<a =
href=3D"https://datatracker.ietf.org/doc/html/rfc8417#section-2.1.1" =
class=3D"">https://datatracker.ietf.org/doc/html/rfc8417#section-2.1.1</a>=
), a password reset event.</div><div class=3D""><br class=3D""></div><div =
class=3D""><pre class=3D"newpage" style=3D"font-size: =
13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: =
page; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">  {
     "iss": "<a href=3D"https://scim.example.com" =
class=3D"">https://scim.example.com</a>",
     "iat": 1458496025,
     "jti": "3d0c3cf797584bd193bd0fb1bd4e7d30",
     "aud": [
       "<a =
href=3D"https://jhub.example.com/Feeds/98d52461fa5bbc879593b7754" =
class=3D"">https://jhub.example.com/Feeds/98d52461fa5bbc879593b7754</a>",
       "<a =
href=3D"https://jhub.example.com/Feeds/5d7604516b1d08641d7676ee7" =
class=3D"">https://jhub.example.com/Feeds/5d7604516b1d08641d7676ee7</a>"
     ],
     "sub": "<a =
href=3D"https://scim.example.com/Users/44f6142df96bd6ab61e7521d9" =
class=3D"">https://scim.example.com/Users/44f6142df96bd6ab61e7521d9</a>",
     "events": {
       "urn:ietf:params:scim:event:passwordReset": {
         "id": "44f6142df96bd6ab61e7521d9"
       },
       "<a href=3D"https://example.com/scim/event/passwordResetExt" =
class=3D"">https://example.com/scim/event/passwordResetExt</a>": {
         "resetAttempts": 5
       }
     }
   }</pre><pre class=3D"newpage" style=3D"font-size: =
13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: =
page; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br =
class=3D""></pre><pre class=3D"newpage" style=3D"margin-top: 0px; =
margin-bottom: 0px; break-before: page; caret-color: rgb(0, 0, =
0);"><font color=3D"#000000" face=3D"Helvetica" class=3D"">Notice under =
the =E2=80=9Cevents=E2=80=9D attribute is a somewhat SCIM like structure =
consisting of an Event ID (urn:ietf:params:scim:event:passwordReset), a =
payload (the id). The example has an extension where additional data is =
provided which in this case is =E2=80=9CresetAttempts=E2=80=9D.</font></pr=
e><div class=3D""><br class=3D""></div></div><div class=3D"">We could =
also have a set of *simple* IDM events indicating: &nbsp;CREATE, MODIFY, =
DELETE and an id. &nbsp;The events don=E2=80=99t even have to contain =
data. You could then have the receiver simply do a GET on the resource =
allowing it to reconcile the current resource. &nbsp;This enables access =
control restrictions to process and keeps event payloads simple in the =
event.</div><div class=3D""><br class=3D""></div><div class=3D"">SET has =
two approved RFCs for exchanging events, namely SET PUSH (RFC8935) and =
POLLING (RFC8936). &nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">Polling mode is great when a management server behind a =
firewall. &nbsp;It can use HTTP LONG POLLING in order to receive events =
in real time. Polling is also good because you can theoretically re-use =
the same credential to pick up events. &nbsp;Push on the other hand =
requires a credential be placed in the publishing side to POST to the =
event receiver.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Push ends up being preferred in situations where a single =
event publisher has many 1000s of subscribers (this was the downfall of =
pubsubhubub). &nbsp;I think for most SCIM cases, we are looking at more =
equal relationships of publishers to subscribers.</div><div class=3D""><br=
 class=3D""></div><div class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); color: rgb(0, 0, 0);" class=3D"">Phil Hunt</span></div><div =
class=3D""><div class=3D""><div dir=3D"auto" style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: =
after-white-space;" class=3D""><div>@independentid</div><div><a =
href=3D"mailto:phil.hunt@independentid.com" =
class=3D"">phil.hunt@independentid.com</a></div><div class=3D""><br =
class=3D""></div></div><br class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Aug 23, 2021, at 4:49 PM, Matt Peterson (mpeterso) &lt;<a =
href=3D"mailto:Matt.Peterson=3D40oneidentity.com@dmarc.ietf.org" =
class=3D"">Matt.Peterson=3D40oneidentity.com@dmarc.ietf.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><meta =
charset=3D"UTF-8" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">The management server in your scenario is a SCIM client. =
&nbsp;</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">If an =
application administrator goes in to the Application Server &nbsp;and =
adds, removes, or modifies account, &nbsp;the Management Server =
&nbsp;has one option when using SCIM -- which is to query the =
Application Server (the SCIM server) for all accounts and then resolve =
the differences between this call and a previous call where all accounts =
were fetched. &nbsp;&nbsp;This is very inefficient. &nbsp;Especially =
when it comes to detecting deleted accounts, there is no other way in =
standard SCIM except to have your Management Server re-load all the =
accounts from your Application server. &nbsp;</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">What you've implemented in your =
Management Server *is* a pure client-side cache scenario as I described =
it. &nbsp;Except that you've recognized that the SCIM spec makes it very =
inefficient to keep your Management Serve up-to-date with changes =
happening "out-of-band" on the Application Servers. &nbsp;</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">So... you implemented a =
notification system whereby your Management Server (SCIM Client) can be =
notified of changes that just happened on the Application Server (the =
SCIM server).</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">Your =
implementation, where the Application Server (SCIM server) notifies your =
Management Server (SCIM client) that a change has occurred *is* one of =
the proposed technical approaches identified by @Phil in a previous post =
to this list and was also mentioned in the BOF. &nbsp;</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">I believe that an approach =
(similar to your implementation ) whereby a SCIM client can subscribe to =
be notified of changes on the SCIM server is an intuitive approach for =
solving the "Syncronization problem"</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">--</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">Matt</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">-----Original =
Message-----</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">From: Danny =
Mayer &lt;</span><a href=3D"mailto:mayer@pdmconsulting.net" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">mayer@pdmconsulting.net</a><span style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Sent: Friday, August 20, 2021 =
8:46 AM</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">To: Matt =
Peterson (mpeterso) &lt;</span><a =
href=3D"mailto:Matt.Peterson@oneidentity.com" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">Matt.Peterson@oneidentity.com</a><span style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&gt;; SCIM WG &lt;</span><a href=3D"mailto:scim@ietf.org" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">scim@ietf.org</a><span style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">&gt;</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Subject: Re: [scim] SCIM Synchronization Problem</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">CAUTION: This email originated =
from outside of the organization. Do not follow guidance, click links, =
or open attachments unless you recognize the sender and know the content =
is safe.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">It's not that =
simple. If an administrator goes in an adds a new account or updates an =
existing account and adds permissions to it, how will the management =
side know? The way I did it was to have the application monitor for =
those changes and notify the management server of the changes. I did =
this via a message queue for our internal applications.</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">The management server needs to =
decide how to handle these violations.</span><br style=3D"caret-color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Danny</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">On 8/19/21 1:33 PM, Matt Peterson (mpeterso) wrote:</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D"">Thank =
you, Danny, for creating a new thread. &nbsp;The following are my =
comments from meeting minutes (some edits):<br class=3D""><br =
class=3D"">There appears to be two use cases for "synchronization":<br =
class=3D""><br class=3D"">&nbsp;&nbsp;1. &nbsp;Constructing and =
enforcing Application authorization models - &nbsp;An application =
(acting as a SCIM client) caches users/groups data from the IdP in order =
to present "user/group pickers" when presenting screens used to =
configure the application &nbsp;authorization rules (RBAC, Policy, or =
ACL). &nbsp;Also, when the application enforces authorization, user and =
group data needs to be immediately available so that authorization =
decisions can be made quickly.<br class=3D""><br class=3D"">&nbsp;&nbsp;2.=
 &nbsp;Identity Management and Governance systems - implement a =
canonical identity model" where all accounts and groups are represented. =
&nbsp;This model is used to build provisioning rules and calculate =
separation of duty violations, attestations, and approvals etc. =
&nbsp;&nbsp;Management-time evaluation of the model needs to be done =
efficiently without external calls to the SCIM service provider.<br =
class=3D""><br class=3D"">Both above use cases, are "client-cache" use =
cases that need only a "one-way" sync (from the SCIM server to the SCIM =
client). &nbsp;&nbsp;To accomplish there are two distinct steps: =
&nbsp;a) download the initial results (users/groups) and, b) keep the =
cached copy of these initial results (user/groups) up to date with =
changes that are being made on the SCIM Service provider.<br =
class=3D""><br class=3D"">I think it could help us narrow down the list =
of suitable approaches if we could agree that "one-way" sync (keeping a =
client-side cache up to date) is our target.<br class=3D""><br =
class=3D"">--<br class=3D"">Matt Peterson<br class=3D""><br =
class=3D"">-----Original Message-----<br class=3D"">From: scim &lt;<a =
href=3D"mailto:scim-bounces@ietf.org" =
class=3D"">scim-bounces@ietf.org</a>&gt; On Behalf Of Danny Mayer<br =
class=3D"">Sent: Wednesday, August 18, 2021 8:34 AM<br class=3D"">To: =
SCIM WG &lt;<a href=3D"mailto:scim@ietf.org" =
class=3D"">scim@ietf.org</a>&gt;<br class=3D"">Subject: [scim] SCIM =
Synchronization Problem<br class=3D""><br class=3D"">CAUTION: This email =
originated from outside of the organization. Do not follow guidance, =
click links, or open attachments unless you recognize the sender and =
know the content is safe.<br class=3D""><br class=3D""><br class=3D"">I =
decided that this needs it's own thread and not be part of the meeting =
minutes.<br class=3D""><br class=3D"">I have had a great deal of =
experience dealing with the user account synchronization problem. Here's =
my view of the problems.<br class=3D""><br class=3D"">I will be calling =
one system Management Server and the other system Application Server. I =
found client/server labels confusing. The Management Server is what I am =
defining to be the server that sends updates to add/update/remove users =
and groups to the Application server whose account, groups and access =
permissions are being managed.<br class=3D""><br class=3D"">First some =
definitions of user accounts. There are usually more than one of each of =
these:<br class=3D"">1. Builtin accounts<br class=3D"">2. =
Special-purpose accounts<br class=3D"">3. Employee<br class=3D"">4. =
Contractor<br class=3D"">5. Agent<br class=3D"">6. Customer<br =
class=3D""><br class=3D"">There may be more.<br class=3D""><br =
class=3D"">1. Builtin accounts: These are accounts that applications =
have and there may be more than one. There is always an admin account =
which can do anything, for example the administrator account in Active =
Directory or a database admin account. The application may have more =
accounts for other purposes.<br class=3D""><br class=3D"">2. =
Special-purpose accounts: These may be set up to provide access to other =
applications, for example a SCIM request to a SCIM REST API should be =
handled by a special account which cannot be used to login via a UI =
interface and only be able to perform certain functions. In addition =
there may be accounts set up to listen for topics or queues on a message =
queue among other possibilities. Keeping separate accounts like this are =
important for tracking in logs and applications.<br class=3D""><br =
class=3D"">3. Employee: These are accounts that employees may login to =
the application.<br class=3D""><br class=3D"">4. Contractors: These =
accounts that a contractor performing work for the company may use to =
log into an application. Unlike Employee accounts these would have an =
expiration date.<br class=3D""><br class=3D"">5. Agent: Accounts like =
this are for external users who may need to manage information for their =
own customers. An example of this is an insurance agent logging in to =
handle an insurance policy for their clients.<br class=3D""><br =
class=3D"">6. Customers: These are where the customers are using the =
application directly. For a bank it's likely to be millions of =
customers. The management platform should not be involved in managing =
these accounts.<br class=3D""><br class=3D"">Let's now look at a few =
example applications.<br class=3D""><br class=3D"">1. Helpdesk<br =
class=3D"">All employees and contractors will need to be able to log =
into a helpdesk application and enter tickets. This means loading =
information about all employees and contractors. For a company with only =
1000 employees that's manageable. For a company with 100K employees, =
it's a bigger challenge.<br class=3D""><br class=3D"">2. Customer =
Support<br class=3D"">Only employees or contractors in the department =
providing customer support need access plus a few other employees. In =
addition identified customers may need accounts.<br class=3D""><br =
class=3D"">3. Expenses<br class=3D"">Not all employees or contractors =
will be submitting expenses so it may not be necessary to have accounts =
for all possible users. This is something that the application owner =
needs to decide.<br class=3D""><br class=3D"">Now let's look at =
logistics.<br class=3D""><br class=3D"">Bulk load:<br class=3D"">Each =
application will need an initial set of accounts set up and for =
something like a helpdesk this could involve load 1000-100,000 =
accounts.<br class=3D"">The information needed could come from either =
the management server or separately, say from an HR system. Many servers =
that I have encountered limit the number of records to something like =
1000, so the pagination requirement is needed for this. Even when =
dealing with a limited subset of employees or contractors you can run =
into this need.<br class=3D""><br class=3D"">Synchronization<br =
class=3D"">An application that is bulk-loaded above may need to be =
synchronized to the management server if the data did not come from the =
management server.<br class=3D""><br class=3D"">Change Management<br =
class=3D"">This is really a synchronization issue as well. Changes =
happen all the time and new employees/contractors need to be added, =
terminated ones removed and updates happen all the time. The best way of =
dealing with this may be to set up a message queue that each application =
can subscribe to and they can take the needed action when it's =
convenient for that application. It's not the only method but it's the =
one I found to be the most helpful. There are two ways of doing that: 1. =
send the complete user information for new accounts, send just the =
change for updating accounts, send the ID for terminated accounts along =
with some meta information. The other method which I have used is just =
to send the ID and whether it's new, updated or terminated.<br =
class=3D""><br class=3D"">I hope this is helpful to the discussion.<br =
class=3D""><br class=3D"">Danny<br class=3D""><br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">scim mailing list<br class=3D""><a =
href=3D"mailto:scim@ietf.org" class=3D"">scim@ietf.org</a><br =
class=3D"">https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%=
2F%2Fwww.<br class=3D""><a href=3D"http://ietf.org/" =
class=3D"">ietf.org</a>%2Fmailman%2Flistinfo%2Fscim&amp;amp;data=3D04%7C01=
%7CMatt.Peterson%<a href=3D"http://40oneidentity.com/" =
class=3D"">40oneidentity.com</a>%7C0502a1bbffb94f6220b808d963e944e9%7C91c3=
69b51c9e439c989c1867ec606603%7C0%7C1%7C637650675822236228%7CUnknown%7CTWFp=
bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D=
%7C3000&amp;amp;sdata=3Dol7Mrjj%2Bx2SGTgQegrvwVNlVeMODf6pxEOc5PTjkK1g%3D&a=
mp;amp;reserved=3D0<br class=3D""><br class=3D""></blockquote><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">scim mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:scim@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">scim@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/scim" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/scim</a></div></blockquot=
e></div><br class=3D""></div></body></html>=

--Apple-Mail=_07A371A5-0D65-4142-818A-A90183AD8BE8--


From nobody Mon Aug 23 18:44:31 2021
Return-Path: <craigmcc@gmail.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 929F63A15FE for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 18:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dIxchAA9-s9y for <scim@ietfa.amsl.com>; Mon, 23 Aug 2021 18:44:22 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 6D7AF3A15F5 for <scim@ietf.org>; Mon, 23 Aug 2021 18:44:22 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id e129so13859656yba.5 for <scim@ietf.org>; Mon, 23 Aug 2021 18:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=yEt+czagNJIpNjZPEXWbBbREFO3K+V3nU7fIdA2JRzY=; b=l7wdG4VsElb6gV6ekRuLcBkBF6K00b1zjJ/79hSF3RfEJb2sxry/1G1vl4TOOyK8X/ VacRmFpTkePh8mqrclAuoeADjUtzRfo8eL8hOUj7myF49gXmwptWSIzp2CbEvnaU2Mur HwuQP/uWvAAwvm0SJb5k5wvqxRJbpojevVJdphwA05p/Y4u82Uy+ThVUCZpbwnZWEBmj 7eu6BgVTzAVANEEEd81sOAHNBmmjS5o86qg823Fhy1sNbgcR+VUexktXtLzBQbZhSmb1 2Beu+PuBHPvkYupM4+2XUq2Aprqg6f3Q51XX6TUNcKw2H09po34HxB3j4dO5RClUbhvR bKsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=yEt+czagNJIpNjZPEXWbBbREFO3K+V3nU7fIdA2JRzY=; b=hU6g85yZtWV1uZ3Ej2WBR3ACxJAK3fRW/TG7zvR+Rixbp1hj39dQ7bj+k9Ch4F94Ff A8XJPFjiblZBl+nS6kUInjWXg0jqYM1FRWXyS8qzlSA9fxl/KU0Mw+upAB9pNiJ9imfG SWKFkXw3fSslaNyaX5PRKTVw103IoIw6IMEmRxWJg5mZHgZIrubUXqqaPEd496h2lVhN RhISm2zkHslMC3SR/fVNat8brreMvX08MQzBaldN/NLDBJaiDfB3zHhgHjRVUWBN/2LL mE9b/ZjSMVYQefg0rlogpqZ1d50avtw2mHndF0GDPTr/Mb1PXqH6ew4SgHTJ7WHUrT0Y p6RA==
X-Gm-Message-State: AOAM533kW+Dtj28Eza13J3HtPIJMmnc6BdbKndh2PtLBajXiQJeUbe6s /37+7941ib2peBFdGWYbnk+ewJnGBWvQqiRDHA0=
X-Google-Smtp-Source: ABdhPJyM9aOvk4Uv8YSH46IUorjQB58km8zKeo4OlYCGpL+2ITLWPyLO4t7qe8BoYj6iOeB6mvMO3loCfG030RWjotg=
X-Received: by 2002:a25:c694:: with SMTP id k142mr11848552ybf.505.1629769459808;  Mon, 23 Aug 2021 18:44:19 -0700 (PDT)
MIME-Version: 1.0
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net> <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
In-Reply-To: <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
Reply-To: craigmcc@gmail.com
From: Craig McClanahan <craigmcc@gmail.com>
Date: Mon, 23 Aug 2021 18:43:42 -0700
Message-ID: <CANgkmLBneyCYFK4Hn0CG4pXDKW5Nfm+Z77dbnhqrGpotaM8EkQ@mail.gmail.com>
To: "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
Cc: Danny Mayer <mayer@pdmconsulting.net>, SCIM WG <scim@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b7c4b805ca4445bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/VKqZ6vZ447jYHnPfvouruSzoc9c>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 01:44:29 -0000

--000000000000b7c4b805ca4445bb
Content-Type: text/plain; charset="UTF-8"

Several years ago (early in the lifetime of the SCIM specification), I was
involved in exactly this kind of situation.  I was trying to extract the
Identity portion of a monolith out into a separate service.  Naturally, as
you'll see in lots of monoliths, the User database information was used for
*lots* of things, not just authentication and authorization, so we couldn't
just remove it from the monolith's database.

>From a SCIM terminology perspective, life was actually pretty clear -- the
monolith was the SCIM server (the source of truth), and the new Identity
Service was the SCIM client.  Creating the initial download mechanism was
no big deal -- one humongous batch transfer (or done in pieces if need be)
and the Identity Service is up to date with the initial snapshot.  But what
happens when:

   - User changes their name (or a bunch of other profile fields)?  Not
   security sensitive, but definitely UI sensitive.  If they are part of the
   data transferred from the SCIM server to the SCIM client, it's definitely
   relevant.
   - User logs on or logs off?  (Groan ... the monolith cared a lot about
   this, because it affects UI like "is this person currently logged in" ...
   even worse, the monolith updated a field in the actual user database row,
   which triggered a gazillion "user change" events (originally internal to
   the monolith) documenting a change that had no other impact than to change
   the last logged in timestamp ... sigh ... performance ... sigh.)
   - User changes their password?  We probably could have absorbed that
   function, but would have required modifications to a bunch of apps out of
   my team's purview, so we didn't.
   - For that matter, *any* change happens between when the snapshot was
   taken, and the Identity Service caught up.

Anyone who has ever tried this trick has most likely run into the same
kinds of issues -- how do you deal with incremental changes that need to be
communicated from the server to the client?  Some of those changes
(passwords, ACLs, account deactivations, etc) are very much time critical.

Our team chose to try to use webhooks from the monolith (SCIM server) back
to the Identity Service (SCIM client), totally out-of-band to anything
defined by SCIM.  This would have worked OK if the webhook technology was
actually reliable and incorporated things like guaranteed forwarding of the
change event messages.  It doesn't work very well, of course, when the
Identity Service hasn't fully processed the initial snapshot yet but
receives a realtime update from the monolith.  In retrospect, this approach
was probably a mistake -- a different messaging technology would have been
better for a narrow point-to-point requirement like this, but would not
have addressed all of the issues.  And what about a more broad-based
notification requirement?

Could we have turned the whole thing around, and made the new Identity
Service the SCIM server, and the monolith the SCIM client?  I suppose, but
it would have required the Identity Service to be involved in a gazillion
things that were not authentication or authorization related, and the need
for some sort of out-of-band "incremental change" event notifications would
have remained, just going in the other direction.

For the SCIM specification, It's the "incremental change" thing that is the
hard nut to crack, IMHO.  But it's actually a bigger problem than that,
endemic to any scenario where you are trying to tear apart a monolith.

Craig McClanahan



On Mon, Aug 23, 2021 at 4:30 PM Matt Peterson (mpeterso) <Matt.Peterson=
40oneidentity.com@dmarc.ietf.org> wrote:

> Thanks for the clarification.
>
> "Client" and "Server" are as used dozens of times in the existing RFCs
> which makes these as useful in understanding the SCIM protocol as they are
> for understanding the HTTP protocol.  In a SCIM protocol exchange there is
> a thing that provides a resource (the server) and a thing that makes a HTTP
> request (GET,POST,PUT,PATCH,DELETE) on the resource (the client).
>
> I think it would be helpful to try and use this generally accepted HTTP
> terminology if we can -- especially when talking about this synchronization
> topic.
>
> Management server <-- SCIM Client
> Application Server <-- SCIM Server
>
> With this clarification, seems to me like your Management Server is using
> SCIM to manage accounts on the Application Server, and that the Management
> Server would benefit from having an up-to-date cache of accounts that are
> on the Application Server(s) even for cases where account
> changes/additions/deletions are made "out of band"  (e.g. directly on the
> Application Server, not initiated by the Management server.)
>
> Did I understand correctly?
>
>
>
> -----Original Message-----
> From: Danny Mayer <mayer@pdmconsulting.net>
> Sent: Friday, August 20, 2021 8:54 AM
> To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <
> scim@ietf.org>
> Subject: Re: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not
> follow guidance, click links, or open attachments unless you recognize the
> sender and know the content is safe.
>
>
> I decided to avoid the client/server naming convention because I find it
> confusing. The system responsible for managing the user accounts and groups
> I have declared to be the Management server. I believe you describe this as
> the "SCIM Client" and is used to GET/POST/PATCH, etc.
> to the Application server to maintain the user accounts and groups. The
> application server is what I believe you call the "SCIM Server". This
> provides the SCIM API's needed.
>
> I find the use of client/server not helpful to understand their role in
> the protocol.
>
> Danny
>
> On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
> > Danny,
> >
> > To help me understand in your post is the "SCIM Client" and what is the
> "SCIM Server" can you tell me which of your components (the Management
> Server or the Application Server) implements SCIM endpoints?
> >
> > The component that acts as a "SCIM Server" is the component that
> provides the of WebAPI endpoints that conform to the SCIM spec.  For
> example, the  /user, /group SCIM endpoints.
> >
> > The component(s) that uses these endpoints to query (GET)  users/groups
> or to create (POST) user/groups is the "SCIM client".
> >
> > --
> > Matt
> >
> > -----Original Message-----
> > From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
> > Sent: Wednesday, August 18, 2021 8:34 AM
> > To: SCIM WG <scim@ietf.org>
> > Subject: [scim] SCIM Synchronization Problem
> >
> > CAUTION: This email originated from outside of the organization. Do not
> follow guidance, click links, or open attachments unless you recognize the
> sender and know the content is safe.
> >
> >
> > I decided that this needs it's own thread and not be part of the meeting
> minutes.
> >
> > I have had a great deal of experience dealing with the user account
> synchronization problem. Here's my view of the problems.
> >
> > I will be calling one system Management Server and the other system
> Application Server. I found client/server labels confusing. The Management
> Server is what I am defining to be the server that sends updates to
> add/update/remove users and groups to the Application server whose account,
> groups and access permissions are being managed.
> >
> > First some definitions of user accounts. There are usually more than one
> of each of these:
> > 1. Builtin accounts
> > 2. Special-purpose accounts
> > 3. Employee
> > 4. Contractor
> > 5. Agent
> > 6. Customer
> >
> > There may be more.
> >
> > 1. Builtin accounts: These are accounts that applications have and there
> may be more than one. There is always an admin account which can do
> anything, for example the administrator account in Active Directory or a
> database admin account. The application may have more accounts for other
> purposes.
> >
> > 2. Special-purpose accounts: These may be set up to provide access to
> other applications, for example a SCIM request to a SCIM REST API should be
> handled by a special account which cannot be used to login via a UI
> interface and only be able to perform certain functions. In addition there
> may be accounts set up to listen for topics or queues on a message queue
> among other possibilities. Keeping separate accounts like this are
> important for tracking in logs and applications.
> >
> > 3. Employee: These are accounts that employees may login to the
> application.
> >
> > 4. Contractors: These accounts that a contractor performing work for the
> company may use to log into an application. Unlike Employee accounts these
> would have an expiration date.
> >
> > 5. Agent: Accounts like this are for external users who may need to
> manage information for their own customers. An example of this is an
> insurance agent logging in to handle an insurance policy for their clients.
> >
> > 6. Customers: These are where the customers are using the application
> directly. For a bank it's likely to be millions of customers. The
> management platform should not be involved in managing these accounts.
> >
> > Let's now look at a few example applications.
> >
> > 1. Helpdesk
> > All employees and contractors will need to be able to log into a
> helpdesk application and enter tickets. This means loading information
> about all employees and contractors. For a company with only 1000 employees
> that's manageable. For a company with 100K employees, it's a bigger
> challenge.
> >
> > 2. Customer Support
> > Only employees or contractors in the department providing customer
> support need access plus a few other employees. In addition identified
> customers may need accounts.
> >
> > 3. Expenses
> > Not all employees or contractors will be submitting expenses so it may
> not be necessary to have accounts for all possible users. This is something
> that the application owner needs to decide.
> >
> > Now let's look at logistics.
> >
> > Bulk load:
> > Each application will need an initial set of accounts set up and for
> something like a helpdesk this could involve load 1000-100,000 accounts.
> > The information needed could come from either the management server or
> separately, say from an HR system. Many servers that I have encountered
> limit the number of records to something like 1000, so the pagination
> requirement is needed for this. Even when dealing with a limited subset of
> employees or contractors you can run into this need.
> >
> > Synchronization
> > An application that is bulk-loaded above may need to be synchronized to
> the management server if the data did not come from the management server.
> >
> > Change Management
> > This is really a synchronization issue as well. Changes happen all the
> time and new employees/contractors need to be added, terminated ones
> removed and updates happen all the time. The best way of dealing with this
> may be to set up a message queue that each application can subscribe to and
> they can take the needed action when it's convenient for that application.
> It's not the only method but it's the one I found to be the most helpful.
> There are two ways of doing that: 1. send the complete user information for
> new accounts, send just the change for updating accounts, send the ID for
> terminated accounts along with some meta information. The other method
> which I have used is just to send the ID and whether it's new, updated or
> terminated.
> >
> > I hope this is helpful to the discussion.
> >
> > Danny
> >
> >
> > _______________________________________________
> > scim mailing list
> > scim@ietf.org
> > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> > ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7CMatt.Peterson%
> > 40oneidentity.com%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439
> > c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d
> > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> > 3000&amp;sdata=BqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;
> > reserved=0
> >
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim
>

--000000000000b7c4b805ca4445bb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Several years ago (early in the lifetime =
of the SCIM specification), I was involved in exactly this kind of situatio=
n.=C2=A0 I was trying to extract the Identity portion of a monolith out int=
o a separate service.=C2=A0 Naturally, as you&#39;ll see in lots of monolit=
hs, the User database information was used for *lots* of things, not just a=
uthentication and authorization, so we couldn&#39;t just remove it from the=
 monolith&#39;s database.<div><br></div><div>From a SCIM terminology perspe=
ctive, life was actually pretty clear -- the monolith was the SCIM server (=
the source of truth), and the new Identity Service was the SCIM client.=C2=
=A0 Creating the initial download mechanism was no big deal -- one humongou=
s batch transfer (or done in pieces if need be) and the Identity Service is=
 up to date with the initial snapshot.=C2=A0 But what happens when:</div><d=
iv><ul><li>User changes their name (or a bunch of other=C2=A0profile fields=
)?=C2=A0 Not security sensitive, but definitely UI sensitive.=C2=A0 If they=
 are part of the data transferred from the SCIM server to the SCIM client, =
it&#39;s definitely relevant.</li><li>User logs on or logs off?=C2=A0 (Groa=
n ... the monolith cared a lot about this, because it affects UI like &quot=
;is this person currently logged in&quot; ... even worse, the monolith upda=
ted a field in the actual user database row, which triggered a gazillion &q=
uot;user change&quot; events (originally internal to the monolith) document=
ing a change that had no other impact than to change the last logged in tim=
estamp ... sigh ... performance ... sigh.)</li><li>User changes their passw=
ord?=C2=A0 We probably could have absorbed that function, but would have re=
quired modifications to a bunch of apps out of my team&#39;s purview, so we=
 didn&#39;t.</li><li>For that matter, *any* change happens between when the=
 snapshot was taken, and the Identity Service caught up.</li></ul><div>Anyo=
ne who has ever tried this trick has most likely run into the same kinds of=
 issues -- how do you deal with incremental changes that need to be communi=
cated from the server to the client?=C2=A0 Some of those changes (passwords=
, ACLs, account deactivations, etc) are very much time critical.</div></div=
><div><br></div><div>Our team chose to try to use webhooks from the monolit=
h (SCIM server) back to the Identity Service (SCIM client), totally out-of-=
band to anything defined by SCIM.=C2=A0 This would have worked OK if the we=
bhook technology was actually reliable and incorporated things like guarant=
eed forwarding of the change event messages.=C2=A0 It doesn&#39;t work very=
 well, of course, when the Identity Service hasn&#39;t fully processed the =
initial snapshot yet but receives a realtime=C2=A0update from the monolith.=
=C2=A0 In retrospect, this approach was probably a mistake -- a different m=
essaging technology would have been better for a narrow point-to-point requ=
irement like this,=C2=A0but would not have addressed=C2=A0all of the=C2=A0i=
ssues.=C2=A0 And what about a more broad-based notification requirement?</d=
iv><div><br></div><div>Could we have turned the whole thing around, and mad=
e the new Identity Service the SCIM server, and the monolith the SCIM clien=
t?=C2=A0 I suppose, but it would have required the Identity Service to be i=
nvolved in a gazillion things that were not authentication or authorization=
 related, and the need for some sort of out-of-band &quot;incremental chang=
e&quot; event notifications would have remained, just going in the other di=
rection.</div><div><br></div><div>For the SCIM specification, It&#39;s the =
&quot;incremental change&quot; thing that is the hard nut to crack, IMHO.=
=C2=A0 But it&#39;s actually a bigger problem than that, endemic to any sce=
nario where you are trying to tear apart a monolith.</div><div><br></div><d=
iv>Craig McClanahan</div><div><br></div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Aug 23, 2021=
 at 4:30 PM Matt Peterson (mpeterso) &lt;Matt.Peterson=3D<a href=3D"mailto:=
40oneidentity.com@dmarc.ietf.org" target=3D"_blank">40oneidentity.com@dmarc=
.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Thanks for the clarification.=C2=A0 <br>
<br>
&quot;Client&quot; and &quot;Server&quot; are as used dozens of times in th=
e existing RFCs which makes these as useful in understanding the SCIM proto=
col as they are for understanding the HTTP protocol.=C2=A0 In a SCIM protoc=
ol exchange there is a thing that provides a resource (the server) and a th=
ing that makes a HTTP request (GET,POST,PUT,PATCH,DELETE) on the resource (=
the client).=C2=A0 <br>
<br>
I think it would be helpful to try and use this generally accepted HTTP ter=
minology if we can -- especially when talking about this synchronization to=
pic.=C2=A0 <br>
<br>
Management server &lt;-- SCIM Client<br>
Application Server &lt;-- SCIM Server<br>
<br>
With this clarification, seems to me like your Management Server is using S=
CIM to manage accounts on the Application Server, and that the Management S=
erver would benefit from having an up-to-date cache of accounts that are on=
 the Application Server(s) even for cases where account changes/additions/d=
eletions are made &quot;out of band&quot;=C2=A0 (e.g. directly on the Appli=
cation Server, not initiated by the Management server.)<br>
<br>
Did I understand correctly?<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Danny Mayer &lt;<a href=3D"mailto:mayer@pdmconsulting.net" target=3D"=
_blank">mayer@pdmconsulting.net</a>&gt; <br>
Sent: Friday, August 20, 2021 8:54 AM<br>
To: Matt Peterson (mpeterso) &lt;<a href=3D"mailto:Matt.Peterson@oneidentit=
y.com" target=3D"_blank">Matt.Peterson@oneidentity.com</a>&gt;; SCIM WG &lt=
;<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a>&gt;<b=
r>
Subject: Re: [scim] SCIM Synchronization Problem<br>
<br>
CAUTION: This email originated from outside of the organization. Do not fol=
low guidance, click links, or open attachments unless you recognize the sen=
der and know the content is safe.<br>
<br>
<br>
I decided to avoid the client/server naming convention because I find it co=
nfusing. The system responsible for managing the user accounts and groups I=
 have declared to be the Management server. I believe you describe this as =
the &quot;SCIM Client&quot; and is used to GET/POST/PATCH, etc.<br>
to the Application server to maintain the user accounts and groups. The app=
lication server is what I believe you call the &quot;SCIM Server&quot;. Thi=
s provides the SCIM API&#39;s needed.<br>
<br>
I find the use of client/server not helpful to understand their role in the=
 protocol.<br>
<br>
Danny<br>
<br>
On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:<br>
&gt; Danny,<br>
&gt;<br>
&gt; To help me understand in your post is the &quot;SCIM Client&quot; and =
what is the &quot;SCIM Server&quot; can you tell me which of your component=
s (the Management Server or the Application Server) implements SCIM endpoin=
ts?<br>
&gt;<br>
&gt; The component that acts as a &quot;SCIM Server&quot; is the component =
that provides the of WebAPI endpoints that conform to the SCIM spec.=C2=A0 =
For example, the=C2=A0 /user, /group SCIM endpoints.<br>
&gt;<br>
&gt; The component(s) that uses these endpoints to query (GET)=C2=A0 users/=
groups or to create (POST) user/groups is the &quot;SCIM client&quot;.<br>
&gt;<br>
&gt; --<br>
&gt; Matt<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: scim &lt;<a href=3D"mailto:scim-bounces@ietf.org" target=3D"_bla=
nk">scim-bounces@ietf.org</a>&gt; On Behalf Of Danny Mayer<br>
&gt; Sent: Wednesday, August 18, 2021 8:34 AM<br>
&gt; To: SCIM WG &lt;<a href=3D"mailto:scim@ietf.org" target=3D"_blank">sci=
m@ietf.org</a>&gt;<br>
&gt; Subject: [scim] SCIM Synchronization Problem<br>
&gt;<br>
&gt; CAUTION: This email originated from outside of the organization. Do no=
t follow guidance, click links, or open attachments unless you recognize th=
e sender and know the content is safe.<br>
&gt;<br>
&gt;<br>
&gt; I decided that this needs it&#39;s own thread and not be part of the m=
eeting minutes.<br>
&gt;<br>
&gt; I have had a great deal of experience dealing with the user account sy=
nchronization problem. Here&#39;s my view of the problems.<br>
&gt;<br>
&gt; I will be calling one system Management Server and the other system Ap=
plication Server. I found client/server labels confusing. The Management Se=
rver is what I am defining to be the server that sends updates to add/updat=
e/remove users and groups to the Application server whose account, groups a=
nd access permissions are being managed.<br>
&gt;<br>
&gt; First some definitions of user accounts. There are usually more than o=
ne of each of these:<br>
&gt; 1. Builtin accounts<br>
&gt; 2. Special-purpose accounts<br>
&gt; 3. Employee<br>
&gt; 4. Contractor<br>
&gt; 5. Agent<br>
&gt; 6. Customer<br>
&gt;<br>
&gt; There may be more.<br>
&gt;<br>
&gt; 1. Builtin accounts: These are accounts that applications have and the=
re may be more than one. There is always an admin account which can do anyt=
hing, for example the administrator account in Active Directory or a databa=
se admin account. The application may have more accounts for other purposes=
.<br>
&gt;<br>
&gt; 2. Special-purpose accounts: These may be set up to provide access to =
other applications, for example a SCIM request to a SCIM REST API should be=
 handled by a special account which cannot be used to login via a UI interf=
ace and only be able to perform certain functions. In addition there may be=
 accounts set up to listen for topics or queues on a message queue among ot=
her possibilities. Keeping separate accounts like this are important for tr=
acking in logs and applications.<br>
&gt;<br>
&gt; 3. Employee: These are accounts that employees may login to the applic=
ation.<br>
&gt;<br>
&gt; 4. Contractors: These accounts that a contractor performing work for t=
he company may use to log into an application. Unlike Employee accounts the=
se would have an expiration date.<br>
&gt;<br>
&gt; 5. Agent: Accounts like this are for external users who may need to ma=
nage information for their own customers. An example of this is an insuranc=
e agent logging in to handle an insurance policy for their clients.<br>
&gt;<br>
&gt; 6. Customers: These are where the customers are using the application =
directly. For a bank it&#39;s likely to be millions of customers. The manag=
ement platform should not be involved in managing these accounts.<br>
&gt;<br>
&gt; Let&#39;s now look at a few example applications.<br>
&gt;<br>
&gt; 1. Helpdesk<br>
&gt; All employees and contractors will need to be able to log into a helpd=
esk application and enter tickets. This means loading information about all=
 employees and contractors. For a company with only 1000 employees that&#39=
;s manageable. For a company with 100K employees, it&#39;s a bigger challen=
ge.<br>
&gt;<br>
&gt; 2. Customer Support<br>
&gt; Only employees or contractors in the department providing customer sup=
port need access plus a few other employees. In addition identified custome=
rs may need accounts.<br>
&gt;<br>
&gt; 3. Expenses<br>
&gt; Not all employees or contractors will be submitting expenses so it may=
 not be necessary to have accounts for all possible users. This is somethin=
g that the application owner needs to decide.<br>
&gt;<br>
&gt; Now let&#39;s look at logistics.<br>
&gt;<br>
&gt; Bulk load:<br>
&gt; Each application will need an initial set of accounts set up and for s=
omething like a helpdesk this could involve load 1000-100,000 accounts.<br>
&gt; The information needed could come from either the management server or=
 separately, say from an HR system. Many servers that I have encountered li=
mit the number of records to something like 1000, so the pagination require=
ment is needed for this. Even when dealing with a limited subset of employe=
es or contractors you can run into this need.<br>
&gt;<br>
&gt; Synchronization<br>
&gt; An application that is bulk-loaded above may need to be synchronized t=
o the management server if the data did not come from the management server=
.<br>
&gt;<br>
&gt; Change Management<br>
&gt; This is really a synchronization issue as well. Changes happen all the=
 time and new employees/contractors need to be added, terminated ones remov=
ed and updates happen all the time. The best way of dealing with this may b=
e to set up a message queue that each application can subscribe to and they=
 can take the needed action when it&#39;s convenient for that application. =
It&#39;s not the only method but it&#39;s the one I found to be the most he=
lpful. There are two ways of doing that: 1. send the complete user informat=
ion for new accounts, send just the change for updating accounts, send the =
ID for terminated accounts along with some meta information. The other meth=
od which I have used is just to send the ID and whether it&#39;s new, updat=
ed or terminated.<br>
&gt;<br>
&gt; I hope this is helpful to the discussion.<br>
&gt;<br>
&gt; Danny<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; scim mailing list<br>
&gt; <a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><b=
r>
&gt; <a href=3D"https://nam12.safelinks.protection.outlook.com/?url=3Dhttps=
%3A%2F%2Fwww" rel=3D"noreferrer" target=3D"_blank">https://nam12.safelinks.=
protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww</a>.<br>
&gt; <a href=3D"http://ietf.org" rel=3D"noreferrer" target=3D"_blank">ietf.=
org</a>%2Fmailman%2Flistinfo%2Fscim&amp;amp;data=3D04%7C01%7CMatt.Peterson%=
<br>
&gt; <a href=3D"http://40oneidentity.com" rel=3D"noreferrer" target=3D"_bla=
nk">40oneidentity.com</a>%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e=
439<br>
&gt; c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d=
<br>
&gt; 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C=
<br>
&gt; 3000&amp;amp;sdata=3DBqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3=
D&amp;amp;<br>
&gt; reserved=3D0<br>
&gt;<br>
<br>
_______________________________________________<br>
scim mailing list<br>
<a href=3D"mailto:scim@ietf.org" target=3D"_blank">scim@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/scim" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/scim</a><br>
</blockquote></div>
</div>

--000000000000b7c4b805ca4445bb--


From nobody Tue Aug 24 08:33:59 2021
Return-Path: <mayer@pdmconsulting.net>
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 2DD063A188B for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:33:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RRNocxdG3Tk0 for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:33:46 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 775DE3A189B for <scim@ietf.org>; Tue, 24 Aug 2021 08:33:39 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GvCnH1VmqzMNWp; Tue, 24 Aug 2021 15:33:39 +0000 (UTC)
To: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>, SCIM WG <scim@ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net> <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <cdd1eb05-0f11-63a1-7454-a85f7586010c@pdmconsulting.net>
Date: Tue, 24 Aug 2021 11:33:38 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/6bK5oQOmwPHnKZ9iIqRRWo9i3Pc>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 15:33:57 -0000

Matt,

What I'm trying to accomplish here is to see the goals of the effort. 
The protocols is just a means to implement the goals. This is the higher 
level of what we are doing.

The answer to your last paragraph is yes, that's what I was trying to 
get to.

Danny

On 8/23/21 7:30 PM, Matt Peterson (mpeterso) wrote:
> Thanks for the clarification.
>
> "Client" and "Server" are as used dozens of times in the existing RFCs which makes these as useful in understanding the SCIM protocol as they are for understanding the HTTP protocol.  In a SCIM protocol exchange there is a thing that provides a resource (the server) and a thing that makes a HTTP request (GET,POST,PUT,PATCH,DELETE) on the resource (the client).
>
> I think it would be helpful to try and use this generally accepted HTTP terminology if we can -- especially when talking about this synchronization topic.
>
> Management server <-- SCIM Client
> Application Server <-- SCIM Server
>
> With this clarification, seems to me like your Management Server is using SCIM to manage accounts on the Application Server, and that the Management Server would benefit from having an up-to-date cache of accounts that are on the Application Server(s) even for cases where account changes/additions/deletions are made "out of band"  (e.g. directly on the Application Server, not initiated by the Management server.)
>
> Did I understand correctly?
>
>
>
> -----Original Message-----
> From: Danny Mayer <mayer@pdmconsulting.net>
> Sent: Friday, August 20, 2021 8:54 AM
> To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <scim@ietf.org>
> Subject: Re: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>
>
> I decided to avoid the client/server naming convention because I find it confusing. The system responsible for managing the user accounts and groups I have declared to be the Management server. I believe you describe this as the "SCIM Client" and is used to GET/POST/PATCH, etc.
> to the Application server to maintain the user accounts and groups. The application server is what I believe you call the "SCIM Server". This provides the SCIM API's needed.
>
> I find the use of client/server not helpful to understand their role in the protocol.
>
> Danny
>
> On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
>> Danny,
>>
>> To help me understand in your post is the "SCIM Client" and what is the "SCIM Server" can you tell me which of your components (the Management Server or the Application Server) implements SCIM endpoints?
>>
>> The component that acts as a "SCIM Server" is the component that provides the of WebAPI endpoints that conform to the SCIM spec.  For example, the  /user, /group SCIM endpoints.
>>
>> The component(s) that uses these endpoints to query (GET)  users/groups or to create (POST) user/groups is the "SCIM client".
>>
>> --
>> Matt
>>
>> -----Original Message-----
>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>> Sent: Wednesday, August 18, 2021 8:34 AM
>> To: SCIM WG <scim@ietf.org>
>> Subject: [scim] SCIM Synchronization Problem
>>
>> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> I decided that this needs it's own thread and not be part of the meeting minutes.
>>
>> I have had a great deal of experience dealing with the user account synchronization problem. Here's my view of the problems.
>>
>> I will be calling one system Management Server and the other system Application Server. I found client/server labels confusing. The Management Server is what I am defining to be the server that sends updates to add/update/remove users and groups to the Application server whose account, groups and access permissions are being managed.
>>
>> First some definitions of user accounts. There are usually more than one of each of these:
>> 1. Builtin accounts
>> 2. Special-purpose accounts
>> 3. Employee
>> 4. Contractor
>> 5. Agent
>> 6. Customer
>>
>> There may be more.
>>
>> 1. Builtin accounts: These are accounts that applications have and there may be more than one. There is always an admin account which can do anything, for example the administrator account in Active Directory or a database admin account. The application may have more accounts for other purposes.
>>
>> 2. Special-purpose accounts: These may be set up to provide access to other applications, for example a SCIM request to a SCIM REST API should be handled by a special account which cannot be used to login via a UI interface and only be able to perform certain functions. In addition there may be accounts set up to listen for topics or queues on a message queue among other possibilities. Keeping separate accounts like this are important for tracking in logs and applications.
>>
>> 3. Employee: These are accounts that employees may login to the application.
>>
>> 4. Contractors: These accounts that a contractor performing work for the company may use to log into an application. Unlike Employee accounts these would have an expiration date.
>>
>> 5. Agent: Accounts like this are for external users who may need to manage information for their own customers. An example of this is an insurance agent logging in to handle an insurance policy for their clients.
>>
>> 6. Customers: These are where the customers are using the application directly. For a bank it's likely to be millions of customers. The management platform should not be involved in managing these accounts.
>>
>> Let's now look at a few example applications.
>>
>> 1. Helpdesk
>> All employees and contractors will need to be able to log into a helpdesk application and enter tickets. This means loading information about all employees and contractors. For a company with only 1000 employees that's manageable. For a company with 100K employees, it's a bigger challenge.
>>
>> 2. Customer Support
>> Only employees or contractors in the department providing customer support need access plus a few other employees. In addition identified customers may need accounts.
>>
>> 3. Expenses
>> Not all employees or contractors will be submitting expenses so it may not be necessary to have accounts for all possible users. This is something that the application owner needs to decide.
>>
>> Now let's look at logistics.
>>
>> Bulk load:
>> Each application will need an initial set of accounts set up and for something like a helpdesk this could involve load 1000-100,000 accounts.
>> The information needed could come from either the management server or separately, say from an HR system. Many servers that I have encountered limit the number of records to something like 1000, so the pagination requirement is needed for this. Even when dealing with a limited subset of employees or contractors you can run into this need.
>>
>> Synchronization
>> An application that is bulk-loaded above may need to be synchronized to the management server if the data did not come from the management server.
>>
>> Change Management
>> This is really a synchronization issue as well. Changes happen all the time and new employees/contractors need to be added, terminated ones removed and updates happen all the time. The best way of dealing with this may be to set up a message queue that each application can subscribe to and they can take the needed action when it's convenient for that application. It's not the only method but it's the one I found to be the most helpful. There are two ways of doing that: 1. send the complete user information for new accounts, send just the change for updating accounts, send the ID for terminated accounts along with some meta information. The other method which I have used is just to send the ID and whether it's new, updated or terminated.
>>
>> I hope this is helpful to the discussion.
>>
>> Danny
>>
>>
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7CMatt.Peterson%
>> 40oneidentity.com%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439
>> c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d
>> 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
>> 3000&amp;sdata=BqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;
>> reserved=0
>>
>


From nobody Tue Aug 24 08:35:20 2021
Return-Path: <mayer@pdmconsulting.net>
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 06BFF3A1898 for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EbxyX5AM4AMN for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:35:12 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB0D03A1894 for <scim@ietf.org>; Tue, 24 Aug 2021 08:35:07 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GvCpx1K1fzMNWp; Tue, 24 Aug 2021 15:35:05 +0000 (UTC)
To: "Matt Peterson (mpeterso)" <Matt.Peterson@oneidentity.com>, SCIM WG <scim@ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB0957823E52255520BD4DB305E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <0f21255e-4ea9-b42d-353d-5c0661e1be5e@pdmconsulting.net> <MWHPR19MB0957723BC8FE476F68EBDEC6E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <6f80bf2c-f27e-dbf1-b5f1-fb9ff6a398f1@pdmconsulting.net>
Date: Tue, 24 Aug 2021 11:35:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <MWHPR19MB0957723BC8FE476F68EBDEC6E1C49@MWHPR19MB0957.namprd19.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/CmlGSXr06_YJZdXYis41Yqdfj-I>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 15:35:19 -0000

Exactly right.

On 8/23/21 7:49 PM, Matt Peterson (mpeterso) wrote:
> The management server in your scenario is a SCIM client.
>
> If an application administrator goes in to the Application Server  and adds, removes, or modifies account,  the Management Server  has one option when using SCIM -- which is to query the Application Server (the SCIM server) for all accounts and then resolve the differences between this call and a previous call where all accounts were fetched.   This is very inefficient.  Especially when it comes to detecting deleted accounts, there is no other way in standard SCIM except to have your Management Server re-load all the accounts from your Application server.
>
> What you've implemented in your Management Server *is* a pure client-side cache scenario as I described it.  Except that you've recognized that the SCIM spec makes it very inefficient to keep your Management Serve up-to-date with changes happening "out-of-band" on the Application Servers.
>
> So... you implemented a notification system whereby your Management Server (SCIM Client) can be notified of changes that just happened on the Application Server (the SCIM server).
>   
> Your implementation, where the Application Server (SCIM server) notifies your Management Server (SCIM client) that a change has occurred *is* one of the proposed technical approaches identified by @Phil in a previous post to this list and was also mentioned in the BOF.
>
> I believe that an approach (similar to your implementation ) whereby a SCIM client can subscribe to be notified of changes on the SCIM server is an intuitive approach for solving the "Syncronization problem"
>
> --
> Matt
>
>
> -----Original Message-----
> From: Danny Mayer <mayer@pdmconsulting.net>
> Sent: Friday, August 20, 2021 8:46 AM
> To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <scim@ietf.org>
> Subject: Re: [scim] SCIM Synchronization Problem
>
> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>
>
> It's not that simple. If an administrator goes in an adds a new account or updates an existing account and adds permissions to it, how will the management side know? The way I did it was to have the application monitor for those changes and notify the management server of the changes. I did this via a message queue for our internal applications.
> The management server needs to decide how to handle these violations.
>
> Danny
>
> On 8/19/21 1:33 PM, Matt Peterson (mpeterso) wrote:
>> Thank you, Danny, for creating a new thread.  The following are my comments from meeting minutes (some edits):
>>
>> There appears to be two use cases for "synchronization":
>>
>>     1.  Constructing and enforcing Application authorization models -  An application (acting as a SCIM client) caches users/groups data from the IdP in order to present "user/group pickers" when presenting screens used to configure the application  authorization rules (RBAC, Policy, or ACL).  Also, when the application enforces authorization, user and group data needs to be immediately available so that authorization decisions can be made quickly.
>>
>>     2.  Identity Management and Governance systems - implement a canonical identity model" where all accounts and groups are represented.  This model is used to build provisioning rules and calculate separation of duty violations, attestations, and approvals etc.   Management-time evaluation of the model needs to be done efficiently without external calls to the SCIM service provider.
>>
>> Both above use cases, are "client-cache" use cases that need only a "one-way" sync (from the SCIM server to the SCIM client).   To accomplish there are two distinct steps:  a) download the initial results (users/groups) and, b) keep the cached copy of these initial results (user/groups) up to date with changes that are being made on the SCIM Service provider.
>>
>> I think it could help us narrow down the list of suitable approaches if we could agree that "one-way" sync (keeping a client-side cache up to date) is our target.
>>
>> --
>> Matt Peterson
>>
>> -----Original Message-----
>> From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>> Sent: Wednesday, August 18, 2021 8:34 AM
>> To: SCIM WG <scim@ietf.org>
>> Subject: [scim] SCIM Synchronization Problem
>>
>> CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.
>>
>>
>> I decided that this needs it's own thread and not be part of the meeting minutes.
>>
>> I have had a great deal of experience dealing with the user account synchronization problem. Here's my view of the problems.
>>
>> I will be calling one system Management Server and the other system Application Server. I found client/server labels confusing. The Management Server is what I am defining to be the server that sends updates to add/update/remove users and groups to the Application server whose account, groups and access permissions are being managed.
>>
>> First some definitions of user accounts. There are usually more than one of each of these:
>> 1. Builtin accounts
>> 2. Special-purpose accounts
>> 3. Employee
>> 4. Contractor
>> 5. Agent
>> 6. Customer
>>
>> There may be more.
>>
>> 1. Builtin accounts: These are accounts that applications have and there may be more than one. There is always an admin account which can do anything, for example the administrator account in Active Directory or a database admin account. The application may have more accounts for other purposes.
>>
>> 2. Special-purpose accounts: These may be set up to provide access to other applications, for example a SCIM request to a SCIM REST API should be handled by a special account which cannot be used to login via a UI interface and only be able to perform certain functions. In addition there may be accounts set up to listen for topics or queues on a message queue among other possibilities. Keeping separate accounts like this are important for tracking in logs and applications.
>>
>> 3. Employee: These are accounts that employees may login to the application.
>>
>> 4. Contractors: These accounts that a contractor performing work for the company may use to log into an application. Unlike Employee accounts these would have an expiration date.
>>
>> 5. Agent: Accounts like this are for external users who may need to manage information for their own customers. An example of this is an insurance agent logging in to handle an insurance policy for their clients.
>>
>> 6. Customers: These are where the customers are using the application directly. For a bank it's likely to be millions of customers. The management platform should not be involved in managing these accounts.
>>
>> Let's now look at a few example applications.
>>
>> 1. Helpdesk
>> All employees and contractors will need to be able to log into a helpdesk application and enter tickets. This means loading information about all employees and contractors. For a company with only 1000 employees that's manageable. For a company with 100K employees, it's a bigger challenge.
>>
>> 2. Customer Support
>> Only employees or contractors in the department providing customer support need access plus a few other employees. In addition identified customers may need accounts.
>>
>> 3. Expenses
>> Not all employees or contractors will be submitting expenses so it may not be necessary to have accounts for all possible users. This is something that the application owner needs to decide.
>>
>> Now let's look at logistics.
>>
>> Bulk load:
>> Each application will need an initial set of accounts set up and for something like a helpdesk this could involve load 1000-100,000 accounts.
>> The information needed could come from either the management server or separately, say from an HR system. Many servers that I have encountered limit the number of records to something like 1000, so the pagination requirement is needed for this. Even when dealing with a limited subset of employees or contractors you can run into this need.
>>
>> Synchronization
>> An application that is bulk-loaded above may need to be synchronized to the management server if the data did not come from the management server.
>>
>> Change Management
>> This is really a synchronization issue as well. Changes happen all the time and new employees/contractors need to be added, terminated ones removed and updates happen all the time. The best way of dealing with this may be to set up a message queue that each application can subscribe to and they can take the needed action when it's convenient for that application. It's not the only method but it's the one I found to be the most helpful. There are two ways of doing that: 1. send the complete user information for new accounts, send just the change for updating accounts, send the ID for terminated accounts along with some meta information. The other method which I have used is just to send the ID and whether it's new, updated or terminated.
>>
>> I hope this is helpful to the discussion.
>>
>> Danny
>>
>>
>> _______________________________________________
>> scim mailing list
>> scim@ietf.org
>> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7CMatt.Peterson%40oneidentity.com%7C0502a1bbffb94f6220b808d963e944e9%7C91c369b51c9e439c989c1867ec606603%7C0%7C1%7C637650675822236228%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=ol7Mrjj%2Bx2SGTgQegrvwVNlVeMODf6pxEOc5PTjkK1g%3D&amp;reserved=0
>>


From nobody Tue Aug 24 08:48:38 2021
Return-Path: <mayer@pdmconsulting.net>
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 6CEDE3A1923 for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 uxMFQgVxJf_C for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 08:48:16 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA163A191D for <scim@ietf.org>; Tue, 24 Aug 2021 08:48:16 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4GvD654GhKzMNWp; Tue, 24 Aug 2021 15:48:13 +0000 (UTC)
To: craigmcc@gmail.com, "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>
Cc: SCIM WG <scim@ietf.org>
References: <e8f9d66c-f356-61b8-d38a-b5288fb9c518@pdmconsulting.net> <MWHPR19MB095771672B28345FA22D6399E1C09@MWHPR19MB0957.namprd19.prod.outlook.com> <10cb88b4-b115-8927-921c-1bde137940fa@pdmconsulting.net> <MWHPR19MB0957D8533A439A99C4E52C97E1C49@MWHPR19MB0957.namprd19.prod.outlook.com> <CANgkmLBneyCYFK4Hn0CG4pXDKW5Nfm+Z77dbnhqrGpotaM8EkQ@mail.gmail.com>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <6062e0f5-736f-b3e6-79b9-6002c72a06fa@pdmconsulting.net>
Date: Tue, 24 Aug 2021 11:48:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <CANgkmLBneyCYFK4Hn0CG4pXDKW5Nfm+Z77dbnhqrGpotaM8EkQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------5CD36CE9981521B1D5E790A0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/H7vMOurfr2lyXxxK5ns9Rw7l3EA>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 15:48:35 -0000

This is a multi-part message in MIME format.
--------------5CD36CE9981521B1D5E790A0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

I've been there and done that. We were lucky enough to have a way to 
differentiate between someone logging in and out and when an update is 
made to something that the SCIM client cares about. We preferred to send 
a notification to a queue that something has changed for the specific ID 
and application and leave it up to the "SCIM client" to query the 
application for the given ID. This had to be a manual operation as the 
SCIM client had no way of reading the queue. The queue was necessary for 
compliance and audit purposes so it wasn't a waste.

Danny

On 8/23/21 9:43 PM, Craig McClanahan wrote:
> Several years ago (early in the lifetime of the SCIM specification), I 
> was involved in exactly this kind of situation.  I was trying to 
> extract the Identity portion of a monolith out into a separate 
> service.  Naturally, as you'll see in lots of monoliths, the User 
> database information was used for *lots* of things, not just 
> authentication and authorization, so we couldn't just remove it from 
> the monolith's database.
>
> From a SCIM terminology perspective, life was actually pretty clear -- 
> the monolith was the SCIM server (the source of truth), and the new 
> Identity Service was the SCIM client.  Creating the initial download 
> mechanism was no big deal -- one humongous batch transfer (or done in 
> pieces if need be) and the Identity Service is up to date with the 
> initial snapshot.  But what happens when:
>
>   * User changes their name (or a bunch of other profile fields)?  Not
>     security sensitive, but definitely UI sensitive.  If they are part
>     of the data transferred from the SCIM server to the SCIM client,
>     it's definitely relevant.
>   * User logs on or logs off?  (Groan ... the monolith cared a lot
>     about this, because it affects UI like "is this person currently
>     logged in" ... even worse, the monolith updated a field in the
>     actual user database row, which triggered a gazillion "user
>     change" events (originally internal to the monolith) documenting a
>     change that had no other impact than to change the last logged in
>     timestamp ... sigh ... performance ... sigh.)
>   * User changes their password?  We probably could have absorbed that
>     function, but would have required modifications to a bunch of apps
>     out of my team's purview, so we didn't.
>   * For that matter, *any* change happens between when the snapshot
>     was taken, and the Identity Service caught up.
>
> Anyone who has ever tried this trick has most likely run into the same 
> kinds of issues -- how do you deal with incremental changes that need 
> to be communicated from the server to the client?  Some of those 
> changes (passwords, ACLs, account deactivations, etc) are very much 
> time critical.
>
> Our team chose to try to use webhooks from the monolith (SCIM server) 
> back to the Identity Service (SCIM client), totally out-of-band to 
> anything defined by SCIM.  This would have worked OK if the webhook 
> technology was actually reliable and incorporated things like 
> guaranteed forwarding of the change event messages.  It doesn't work 
> very well, of course, when the Identity Service hasn't fully processed 
> the initial snapshot yet but receives a realtime update from the 
> monolith.  In retrospect, this approach was probably a mistake -- a 
> different messaging technology would have been better for a narrow 
> point-to-point requirement like this, but would not have addressed all 
> of the issues.  And what about a more broad-based notification 
> requirement?
>
> Could we have turned the whole thing around, and made the new Identity 
> Service the SCIM server, and the monolith the SCIM client?  I suppose, 
> but it would have required the Identity Service to be involved in a 
> gazillion things that were not authentication or authorization 
> related, and the need for some sort of out-of-band "incremental 
> change" event notifications would have remained, just going in the 
> other direction.
>
> For the SCIM specification, It's the "incremental change" thing that 
> is the hard nut to crack, IMHO.  But it's actually a bigger problem 
> than that, endemic to any scenario where you are trying to tear apart 
> a monolith.
>
> Craig McClanahan
>
>
>
> On Mon, Aug 23, 2021 at 4:30 PM Matt Peterson (mpeterso) 
> <Matt.Peterson=40oneidentity.com@dmarc.ietf.org 
> <mailto:40oneidentity.com@dmarc.ietf.org>> wrote:
>
>     Thanks for the clarification.
>
>     "Client" and "Server" are as used dozens of times in the existing
>     RFCs which makes these as useful in understanding the SCIM
>     protocol as they are for understanding the HTTP protocol.  In a
>     SCIM protocol exchange there is a thing that provides a resource
>     (the server) and a thing that makes a HTTP request
>     (GET,POST,PUT,PATCH,DELETE) on the resource (the client).
>
>     I think it would be helpful to try and use this generally accepted
>     HTTP terminology if we can -- especially when talking about this
>     synchronization topic.
>
>     Management server <-- SCIM Client
>     Application Server <-- SCIM Server
>
>     With this clarification, seems to me like your Management Server
>     is using SCIM to manage accounts on the Application Server, and
>     that the Management Server would benefit from having an up-to-date
>     cache of accounts that are on the Application Server(s) even for
>     cases where account changes/additions/deletions are made "out of
>     band"  (e.g. directly on the Application Server, not initiated by
>     the Management server.)
>
>     Did I understand correctly?
>
>
>
>     -----Original Message-----
>     From: Danny Mayer <mayer@pdmconsulting.net
>     <mailto:mayer@pdmconsulting.net>>
>     Sent: Friday, August 20, 2021 8:54 AM
>     To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com
>     <mailto:Matt.Peterson@oneidentity.com>>; SCIM WG <scim@ietf.org
>     <mailto:scim@ietf.org>>
>     Subject: Re: [scim] SCIM Synchronization Problem
>
>     CAUTION: This email originated from outside of the organization.
>     Do not follow guidance, click links, or open attachments unless
>     you recognize the sender and know the content is safe.
>
>
>     I decided to avoid the client/server naming convention because I
>     find it confusing. The system responsible for managing the user
>     accounts and groups I have declared to be the Management server. I
>     believe you describe this as the "SCIM Client" and is used to
>     GET/POST/PATCH, etc.
>     to the Application server to maintain the user accounts and
>     groups. The application server is what I believe you call the
>     "SCIM Server". This provides the SCIM API's needed.
>
>     I find the use of client/server not helpful to understand their
>     role in the protocol.
>
>     Danny
>
>     On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
>     > Danny,
>     >
>     > To help me understand in your post is the "SCIM Client" and what
>     is the "SCIM Server" can you tell me which of your components (the
>     Management Server or the Application Server) implements SCIM
>     endpoints?
>     >
>     > The component that acts as a "SCIM Server" is the component that
>     provides the of WebAPI endpoints that conform to the SCIM spec. 
>     For example, the  /user, /group SCIM endpoints.
>     >
>     > The component(s) that uses these endpoints to query (GET) 
>     users/groups or to create (POST) user/groups is the "SCIM client".
>     >
>     > --
>     > Matt
>     >
>     > -----Original Message-----
>     > From: scim <scim-bounces@ietf.org
>     <mailto:scim-bounces@ietf.org>> On Behalf Of Danny Mayer
>     > Sent: Wednesday, August 18, 2021 8:34 AM
>     > To: SCIM WG <scim@ietf.org <mailto:scim@ietf.org>>
>     > Subject: [scim] SCIM Synchronization Problem
>     >
>     > CAUTION: This email originated from outside of the organization.
>     Do not follow guidance, click links, or open attachments unless
>     you recognize the sender and know the content is safe.
>     >
>     >
>     > I decided that this needs it's own thread and not be part of the
>     meeting minutes.
>     >
>     > I have had a great deal of experience dealing with the user
>     account synchronization problem. Here's my view of the problems.
>     >
>     > I will be calling one system Management Server and the other
>     system Application Server. I found client/server labels confusing.
>     The Management Server is what I am defining to be the server that
>     sends updates to add/update/remove users and groups to the
>     Application server whose account, groups and access permissions
>     are being managed.
>     >
>     > First some definitions of user accounts. There are usually more
>     than one of each of these:
>     > 1. Builtin accounts
>     > 2. Special-purpose accounts
>     > 3. Employee
>     > 4. Contractor
>     > 5. Agent
>     > 6. Customer
>     >
>     > There may be more.
>     >
>     > 1. Builtin accounts: These are accounts that applications have
>     and there may be more than one. There is always an admin account
>     which can do anything, for example the administrator account in
>     Active Directory or a database admin account. The application may
>     have more accounts for other purposes.
>     >
>     > 2. Special-purpose accounts: These may be set up to provide
>     access to other applications, for example a SCIM request to a SCIM
>     REST API should be handled by a special account which cannot be
>     used to login via a UI interface and only be able to perform
>     certain functions. In addition there may be accounts set up to
>     listen for topics or queues on a message queue among other
>     possibilities. Keeping separate accounts like this are important
>     for tracking in logs and applications.
>     >
>     > 3. Employee: These are accounts that employees may login to the
>     application.
>     >
>     > 4. Contractors: These accounts that a contractor performing work
>     for the company may use to log into an application. Unlike
>     Employee accounts these would have an expiration date.
>     >
>     > 5. Agent: Accounts like this are for external users who may need
>     to manage information for their own customers. An example of this
>     is an insurance agent logging in to handle an insurance policy for
>     their clients.
>     >
>     > 6. Customers: These are where the customers are using the
>     application directly. For a bank it's likely to be millions of
>     customers. The management platform should not be involved in
>     managing these accounts.
>     >
>     > Let's now look at a few example applications.
>     >
>     > 1. Helpdesk
>     > All employees and contractors will need to be able to log into a
>     helpdesk application and enter tickets. This means loading
>     information about all employees and contractors. For a company
>     with only 1000 employees that's manageable. For a company with
>     100K employees, it's a bigger challenge.
>     >
>     > 2. Customer Support
>     > Only employees or contractors in the department providing
>     customer support need access plus a few other employees. In
>     addition identified customers may need accounts.
>     >
>     > 3. Expenses
>     > Not all employees or contractors will be submitting expenses so
>     it may not be necessary to have accounts for all possible users.
>     This is something that the application owner needs to decide.
>     >
>     > Now let's look at logistics.
>     >
>     > Bulk load:
>     > Each application will need an initial set of accounts set up and
>     for something like a helpdesk this could involve load 1000-100,000
>     accounts.
>     > The information needed could come from either the management
>     server or separately, say from an HR system. Many servers that I
>     have encountered limit the number of records to something like
>     1000, so the pagination requirement is needed for this. Even when
>     dealing with a limited subset of employees or contractors you can
>     run into this need.
>     >
>     > Synchronization
>     > An application that is bulk-loaded above may need to be
>     synchronized to the management server if the data did not come
>     from the management server.
>     >
>     > Change Management
>     > This is really a synchronization issue as well. Changes happen
>     all the time and new employees/contractors need to be added,
>     terminated ones removed and updates happen all the time. The best
>     way of dealing with this may be to set up a message queue that
>     each application can subscribe to and they can take the needed
>     action when it's convenient for that application. It's not the
>     only method but it's the one I found to be the most helpful. There
>     are two ways of doing that: 1. send the complete user information
>     for new accounts, send just the change for updating accounts, send
>     the ID for terminated accounts along with some meta information.
>     The other method which I have used is just to send the ID and
>     whether it's new, updated or terminated.
>     >
>     > I hope this is helpful to the discussion.
>     >
>     > Danny
>     >
>     >
>     > _______________________________________________
>     > scim mailing list
>     > scim@ietf.org <mailto:scim@ietf.org>
>     >
>     https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
>     <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww>.
>     > ietf.org
>     <http://ietf.org>%2Fmailman%2Flistinfo%2Fscim&amp;data=04%7C01%7CMatt.Peterson%
>     > 40oneidentity.com
>     <http://40oneidentity.com>%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439
>     >
>     c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d
>     >
>     8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
>     >
>     3000&amp;sdata=BqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;
>     > reserved=0
>     >
>
>     _______________________________________________
>     scim mailing list
>     scim@ietf.org <mailto:scim@ietf.org>
>     https://www.ietf.org/mailman/listinfo/scim
>     <https://www.ietf.org/mailman/listinfo/scim>
>

--------------5CD36CE9981521B1D5E790A0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>I've been there and done that. We were lucky enough to have a way
      to differentiate between someone logging in and out and when an
      update is made to something that the SCIM client cares about. We
      preferred to send a notification to a queue that something has
      changed for the specific ID and application and leave it up to the
      "SCIM client" to query the application for the given ID. This had
      to be a manual operation as the SCIM client had no way of reading
      the queue. The queue was necessary for compliance and audit
      purposes so it wasn't a waste.</p>
    <p>Danny<br>
    </p>
    <div class="moz-cite-prefix">On 8/23/21 9:43 PM, Craig McClanahan
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CANgkmLBneyCYFK4Hn0CG4pXDKW5Nfm+Z77dbnhqrGpotaM8EkQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">Several years ago (early in the lifetime of the
          SCIM specification), I was involved in exactly this kind of
          situation.  I was trying to extract the Identity portion of a
          monolith out into a separate service.  Naturally, as you'll
          see in lots of monoliths, the User database information was
          used for *lots* of things, not just authentication and
          authorization, so we couldn't just remove it from the
          monolith's database.
          <div><br>
          </div>
          <div>From a SCIM terminology perspective, life was actually
            pretty clear -- the monolith was the SCIM server (the source
            of truth), and the new Identity Service was the SCIM
            client.  Creating the initial download mechanism was no big
            deal -- one humongous batch transfer (or done in pieces if
            need be) and the Identity Service is up to date with the
            initial snapshot.  But what happens when:</div>
          <div>
            <ul>
              <li>User changes their name (or a bunch of other profile
                fields)?  Not security sensitive, but definitely UI
                sensitive.  If they are part of the data transferred
                from the SCIM server to the SCIM client, it's definitely
                relevant.</li>
              <li>User logs on or logs off?  (Groan ... the monolith
                cared a lot about this, because it affects UI like "is
                this person currently logged in" ... even worse, the
                monolith updated a field in the actual user database
                row, which triggered a gazillion "user change" events
                (originally internal to the monolith) documenting a
                change that had no other impact than to change the last
                logged in timestamp ... sigh ... performance ... sigh.)</li>
              <li>User changes their password?  We probably could have
                absorbed that function, but would have required
                modifications to a bunch of apps out of my team's
                purview, so we didn't.</li>
              <li>For that matter, *any* change happens between when the
                snapshot was taken, and the Identity Service caught up.</li>
            </ul>
            <div>Anyone who has ever tried this trick has most likely
              run into the same kinds of issues -- how do you deal with
              incremental changes that need to be communicated from the
              server to the client?  Some of those changes (passwords,
              ACLs, account deactivations, etc) are very much time
              critical.</div>
          </div>
          <div><br>
          </div>
          <div>Our team chose to try to use webhooks from the monolith
            (SCIM server) back to the Identity Service (SCIM client),
            totally out-of-band to anything defined by SCIM.  This would
            have worked OK if the webhook technology was actually
            reliable and incorporated things like guaranteed forwarding
            of the change event messages.  It doesn't work very well, of
            course, when the Identity Service hasn't fully processed the
            initial snapshot yet but receives a realtime update from the
            monolith.  In retrospect, this approach was probably a
            mistake -- a different messaging technology would have been
            better for a narrow point-to-point requirement like
            this, but would not have addressed all of the issues.  And
            what about a more broad-based notification requirement?</div>
          <div><br>
          </div>
          <div>Could we have turned the whole thing around, and made the
            new Identity Service the SCIM server, and the monolith the
            SCIM client?  I suppose, but it would have required the
            Identity Service to be involved in a gazillion things that
            were not authentication or authorization related, and the
            need for some sort of out-of-band "incremental change" event
            notifications would have remained, just going in the other
            direction.</div>
          <div><br>
          </div>
          <div>For the SCIM specification, It's the "incremental change"
            thing that is the hard nut to crack, IMHO.  But it's
            actually a bigger problem than that, endemic to any scenario
            where you are trying to tear apart a monolith.</div>
          <div><br>
          </div>
          <div>Craig McClanahan</div>
          <div><br>
          </div>
          <div><br>
          </div>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Mon, Aug 23, 2021 at 4:30
            PM Matt Peterson (mpeterso) &lt;Matt.Peterson=<a
              href="mailto:40oneidentity.com@dmarc.ietf.org"
              target="_blank" moz-do-not-send="true">40oneidentity.com@dmarc.ietf.org</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">Thanks for the
            clarification.  <br>
            <br>
            "Client" and "Server" are as used dozens of times in the
            existing RFCs which makes these as useful in understanding
            the SCIM protocol as they are for understanding the HTTP
            protocol.  In a SCIM protocol exchange there is a thing that
            provides a resource (the server) and a thing that makes a
            HTTP request (GET,POST,PUT,PATCH,DELETE) on the resource
            (the client).  <br>
            <br>
            I think it would be helpful to try and use this generally
            accepted HTTP terminology if we can -- especially when
            talking about this synchronization topic.  <br>
            <br>
            Management server &lt;-- SCIM Client<br>
            Application Server &lt;-- SCIM Server<br>
            <br>
            With this clarification, seems to me like your Management
            Server is using SCIM to manage accounts on the Application
            Server, and that the Management Server would benefit from
            having an up-to-date cache of accounts that are on the
            Application Server(s) even for cases where account
            changes/additions/deletions are made "out of band"  (e.g.
            directly on the Application Server, not initiated by the
            Management server.)<br>
            <br>
            Did I understand correctly?<br>
            <br>
            <br>
            <br>
            -----Original Message-----<br>
            From: Danny Mayer &lt;<a
              href="mailto:mayer@pdmconsulting.net" target="_blank"
              moz-do-not-send="true">mayer@pdmconsulting.net</a>&gt; <br>
            Sent: Friday, August 20, 2021 8:54 AM<br>
            To: Matt Peterson (mpeterso) &lt;<a
              href="mailto:Matt.Peterson@oneidentity.com"
              target="_blank" moz-do-not-send="true">Matt.Peterson@oneidentity.com</a>&gt;;
            SCIM WG &lt;<a href="mailto:scim@ietf.org" target="_blank"
              moz-do-not-send="true">scim@ietf.org</a>&gt;<br>
            Subject: Re: [scim] SCIM Synchronization Problem<br>
            <br>
            CAUTION: This email originated from outside of the
            organization. Do not follow guidance, click links, or open
            attachments unless you recognize the sender and know the
            content is safe.<br>
            <br>
            <br>
            I decided to avoid the client/server naming convention
            because I find it confusing. The system responsible for
            managing the user accounts and groups I have declared to be
            the Management server. I believe you describe this as the
            "SCIM Client" and is used to GET/POST/PATCH, etc.<br>
            to the Application server to maintain the user accounts and
            groups. The application server is what I believe you call
            the "SCIM Server". This provides the SCIM API's needed.<br>
            <br>
            I find the use of client/server not helpful to understand
            their role in the protocol.<br>
            <br>
            Danny<br>
            <br>
            On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:<br>
            &gt; Danny,<br>
            &gt;<br>
            &gt; To help me understand in your post is the "SCIM Client"
            and what is the "SCIM Server" can you tell me which of your
            components (the Management Server or the Application Server)
            implements SCIM endpoints?<br>
            &gt;<br>
            &gt; The component that acts as a "SCIM Server" is the
            component that provides the of WebAPI endpoints that conform
            to the SCIM spec.  For example, the  /user, /group SCIM
            endpoints.<br>
            &gt;<br>
            &gt; The component(s) that uses these endpoints to query
            (GET)  users/groups or to create (POST) user/groups is the
            "SCIM client".<br>
            &gt;<br>
            &gt; --<br>
            &gt; Matt<br>
            &gt;<br>
            &gt; -----Original Message-----<br>
            &gt; From: scim &lt;<a href="mailto:scim-bounces@ietf.org"
              target="_blank" moz-do-not-send="true">scim-bounces@ietf.org</a>&gt;
            On Behalf Of Danny Mayer<br>
            &gt; Sent: Wednesday, August 18, 2021 8:34 AM<br>
            &gt; To: SCIM WG &lt;<a href="mailto:scim@ietf.org"
              target="_blank" moz-do-not-send="true">scim@ietf.org</a>&gt;<br>
            &gt; Subject: [scim] SCIM Synchronization Problem<br>
            &gt;<br>
            &gt; CAUTION: This email originated from outside of the
            organization. Do not follow guidance, click links, or open
            attachments unless you recognize the sender and know the
            content is safe.<br>
            &gt;<br>
            &gt;<br>
            &gt; I decided that this needs it's own thread and not be
            part of the meeting minutes.<br>
            &gt;<br>
            &gt; I have had a great deal of experience dealing with the
            user account synchronization problem. Here's my view of the
            problems.<br>
            &gt;<br>
            &gt; I will be calling one system Management Server and the
            other system Application Server. I found client/server
            labels confusing. The Management Server is what I am
            defining to be the server that sends updates to
            add/update/remove users and groups to the Application server
            whose account, groups and access permissions are being
            managed.<br>
            &gt;<br>
            &gt; First some definitions of user accounts. There are
            usually more than one of each of these:<br>
            &gt; 1. Builtin accounts<br>
            &gt; 2. Special-purpose accounts<br>
            &gt; 3. Employee<br>
            &gt; 4. Contractor<br>
            &gt; 5. Agent<br>
            &gt; 6. Customer<br>
            &gt;<br>
            &gt; There may be more.<br>
            &gt;<br>
            &gt; 1. Builtin accounts: These are accounts that
            applications have and there may be more than one. There is
            always an admin account which can do anything, for example
            the administrator account in Active Directory or a database
            admin account. The application may have more accounts for
            other purposes.<br>
            &gt;<br>
            &gt; 2. Special-purpose accounts: These may be set up to
            provide access to other applications, for example a SCIM
            request to a SCIM REST API should be handled by a special
            account which cannot be used to login via a UI interface and
            only be able to perform certain functions. In addition there
            may be accounts set up to listen for topics or queues on a
            message queue among other possibilities. Keeping separate
            accounts like this are important for tracking in logs and
            applications.<br>
            &gt;<br>
            &gt; 3. Employee: These are accounts that employees may
            login to the application.<br>
            &gt;<br>
            &gt; 4. Contractors: These accounts that a contractor
            performing work for the company may use to log into an
            application. Unlike Employee accounts these would have an
            expiration date.<br>
            &gt;<br>
            &gt; 5. Agent: Accounts like this are for external users who
            may need to manage information for their own customers. An
            example of this is an insurance agent logging in to handle
            an insurance policy for their clients.<br>
            &gt;<br>
            &gt; 6. Customers: These are where the customers are using
            the application directly. For a bank it's likely to be
            millions of customers. The management platform should not be
            involved in managing these accounts.<br>
            &gt;<br>
            &gt; Let's now look at a few example applications.<br>
            &gt;<br>
            &gt; 1. Helpdesk<br>
            &gt; All employees and contractors will need to be able to
            log into a helpdesk application and enter tickets. This
            means loading information about all employees and
            contractors. For a company with only 1000 employees that's
            manageable. For a company with 100K employees, it's a bigger
            challenge.<br>
            &gt;<br>
            &gt; 2. Customer Support<br>
            &gt; Only employees or contractors in the department
            providing customer support need access plus a few other
            employees. In addition identified customers may need
            accounts.<br>
            &gt;<br>
            &gt; 3. Expenses<br>
            &gt; Not all employees or contractors will be submitting
            expenses so it may not be necessary to have accounts for all
            possible users. This is something that the application owner
            needs to decide.<br>
            &gt;<br>
            &gt; Now let's look at logistics.<br>
            &gt;<br>
            &gt; Bulk load:<br>
            &gt; Each application will need an initial set of accounts
            set up and for something like a helpdesk this could involve
            load 1000-100,000 accounts.<br>
            &gt; The information needed could come from either the
            management server or separately, say from an HR system. Many
            servers that I have encountered limit the number of records
            to something like 1000, so the pagination requirement is
            needed for this. Even when dealing with a limited subset of
            employees or contractors you can run into this need.<br>
            &gt;<br>
            &gt; Synchronization<br>
            &gt; An application that is bulk-loaded above may need to be
            synchronized to the management server if the data did not
            come from the management server.<br>
            &gt;<br>
            &gt; Change Management<br>
            &gt; This is really a synchronization issue as well. Changes
            happen all the time and new employees/contractors need to be
            added, terminated ones removed and updates happen all the
            time. The best way of dealing with this may be to set up a
            message queue that each application can subscribe to and
            they can take the needed action when it's convenient for
            that application. It's not the only method but it's the one
            I found to be the most helpful. There are two ways of doing
            that: 1. send the complete user information for new
            accounts, send just the change for updating accounts, send
            the ID for terminated accounts along with some meta
            information. The other method which I have used is just to
            send the ID and whether it's new, updated or terminated.<br>
            &gt;<br>
            &gt; I hope this is helpful to the discussion.<br>
            &gt;<br>
            &gt; Danny<br>
            &gt;<br>
            &gt;<br>
            &gt; _______________________________________________<br>
            &gt; scim mailing list<br>
            &gt; <a href="mailto:scim@ietf.org" target="_blank"
              moz-do-not-send="true">scim@ietf.org</a><br>
            &gt; <a
href="https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww</a>.<br>
            &gt; <a href="http://ietf.org" rel="noreferrer"
              target="_blank" moz-do-not-send="true">ietf.org</a>%2Fmailman%2Flistinfo%2Fscim&amp;amp;data=04%7C01%7CMatt.Peterson%<br>
            &gt; <a href="http://40oneidentity.com" rel="noreferrer"
              target="_blank" moz-do-not-send="true">40oneidentity.com</a>%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439<br>
            &gt;
            c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d<br>
            &gt;
            8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C<br>
            &gt;
3000&amp;amp;sdata=BqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;amp;<br>
            &gt; reserved=0<br>
            &gt;<br>
            <br>
            _______________________________________________<br>
            scim mailing list<br>
            <a href="mailto:scim@ietf.org" target="_blank"
              moz-do-not-send="true">scim@ietf.org</a><br>
            <a href="https://www.ietf.org/mailman/listinfo/scim"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/scim</a><br>
          </blockquote>
        </div>
      </div>
    </blockquote>
  </body>
</html>

--------------5CD36CE9981521B1D5E790A0--


From nobody Tue Aug 24 09:10:32 2021
Return-Path: <phil.hunt@independentid.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 6E2663A1B9A for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 09:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=independentid-com.20150623.gappssmtp.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 kezIfQj1vpfY for <scim@ietfa.amsl.com>; Tue, 24 Aug 2021 09:10:23 -0700 (PDT)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 75E223A1B9B for <scim@ietf.org>; Tue, 24 Aug 2021 09:10:23 -0700 (PDT)
Received: by mail-pl1-x629.google.com with SMTP id a5so12529651plh.5 for <scim@ietf.org>; Tue, 24 Aug 2021 09:10:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=independentid-com.20150623.gappssmtp.com; s=20150623; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Z3y6I0rD7KmRd/JukNdaN8Au7oNUC9IIo4a9RFmHtMc=; b=tYYRItcAlDwSeXWbyzeEueZZE7JGpqBCFAy9/v8zavo3nICbMtbKazSXn+fp26KTxZ XgKOaRw7Ju5EFpcY8m8ALBwwYf9GolYNIPGqB8Y/DEmllQVvwSybksGjI+hYvqAc4uUn au6IMeMpk1ShuvwANVdCb8MyF+2rzx/zeMrN8aZe4Y83zLTBnsNtXre2BY6K8RMByz3Z kXgps9MuDSWIXHepL8rJ4ghaEWN6aQY68lRNR2QYLUYqm0PXHJyhSEzQBqTuU/EwC9Zm QRlg0UV6xLK9YVjlhM60LuAUGfsGbUdvtL7hZmiJdoEPs1f7KriqbBFIPtI47C02LtR1 HIVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Z3y6I0rD7KmRd/JukNdaN8Au7oNUC9IIo4a9RFmHtMc=; b=UTC5bkSn85I9yu/RiWmeeJIgGtdixVMKdSui06FF2eBB/On2tVrR1SkdJufCRWR4H4 RIzZrVT3oh8bOOs5l2IQgpxHfBX7c9/eJuXeOZrqdOlJQbtwPNI6vB3VyicDKtU0NXVg GQ4q+VkT/YKnsgK94K/fQY0k4Vh7O+xKLtOsNFNGRmA0BKIpiATKQyaIfbG/0z50rjRU 93u97aa4HJC8XODnq/BdmjHINeaBR95RIF41fP3ubPIUyQON8ip+XqQWgHUVCy7OaLiG /Xelq7beqzCVS4gvVype4zZAyNe+7LWSrVpl+VcRol0ltHMz4o9K7QVRGYxIljfD7rmC peYw==
X-Gm-Message-State: AOAM532mxdJ0xxu+Vy2tat2DrmsXmdz4W3qA19ml80GF0XpoypC8j71M p6J2BwE90eqADkGZ2e1YHT30LQ==
X-Google-Smtp-Source: ABdhPJw0Wv+64mjr20VVVycogvpqlvXIooCBkdUYOgxBSIED/AE0k5zIX0+32jmo3/gcA1NUxrFZ1w==
X-Received: by 2002:a17:90b:1981:: with SMTP id mv1mr5107749pjb.45.1629821420754;  Tue, 24 Aug 2021 09:10:20 -0700 (PDT)
Received: from smtpclient.apple (node-1w7jr9qrfoxx9v2e839ysri3r.ipv6.telus.net. [2001:569:7a71:1d00:99c2:dc4a:9c9d:4867]) by smtp.gmail.com with ESMTPSA id q21sm22413546pgk.71.2021.08.24.09.10.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 24 Aug 2021 09:10:20 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-755B77A8-4C45-41B4-964B-29940A439E17
Content-Transfer-Encoding: 7bit
From: Phillip Hunt <phil.hunt@independentid.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 24 Aug 2021 09:10:19 -0700
Message-Id: <77332A5A-F740-4191-BCFF-137CA2B378BD@independentid.com>
References: <6062e0f5-736f-b3e6-79b9-6002c72a06fa@pdmconsulting.net>
Cc: craigmcc@gmail.com, "Matt Peterson (mpeterso)" <Matt.Peterson=40oneidentity.com@dmarc.ietf.org>, SCIM WG <scim@ietf.org>
In-Reply-To: <6062e0f5-736f-b3e6-79b9-6002c72a06fa@pdmconsulting.net>
To: Danny Mayer <mayer@pdmconsulting.net>
X-Mailer: iPhone Mail (18G82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/bsFI9W0EmFtBozbKf2zEVvj6T9Q>
Subject: Re: [scim] SCIM Synchronization Problem
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 24 Aug 2021 16:10:31 -0000

--Apple-Mail-755B77A8-4C45-41B4-964B-29940A439E17
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

So a requirement here is to indicate what schema is of interest for sync. An=
y notification method needs to be filterable on at least schema-id and poten=
tially specific attributes. Eg a receiver may only be interested in events r=
elated to roles.=20

The also shows why pre-conditioned HEAD queries couldn=E2=80=99t be used. Th=
ese types of queries can ask: does this url exist? Has this resource changed=
 since this etag or date.  Obviously any change to content changes the hash a=
nd mod-dates.=20

Obviously one of the downsides to attaching session information to the user r=
esource is affecting change rates. Why not have separate session resources p=
oint to users?  Their change rate and lifecycle are much different than that=
 of a user. A best practice would be to keep this data separate from the use=
r.=20
IOW -> how much do we need to accommodate in sync?  Should we be having a se=
parate session schema discussion?

Phil

> On Aug 24, 2021, at 8:49 AM, Danny Mayer <mayer@pdmconsulting.net> wrote:
>=20
> =EF=BB=BF
> I've been there and done that. We were lucky enough to have a way to diffe=
rentiate between someone logging in and out and when an update is made to so=
mething that the SCIM client cares about. We preferred to send a notificatio=
n to a queue that something has changed for the specific ID and application a=
nd leave it up to the "SCIM client" to query the application for the given I=
D. This had to be a manual operation as the SCIM client had no way of readin=
g the queue. The queue was necessary for compliance and audit purposes so it=
 wasn't a waste.
>=20
> Danny
>=20
> On 8/23/21 9:43 PM, Craig McClanahan wrote:
>> Several years ago (early in the lifetime of the SCIM specification), I wa=
s involved in exactly this kind of situation.  I was trying to extract the I=
dentity portion of a monolith out into a separate service.  Naturally, as yo=
u'll see in lots of monoliths, the User database information was used for *l=
ots* of things, not just authentication and authorization, so we couldn't ju=
st remove it from the monolith's database.
>>=20
>> =46rom a SCIM terminology perspective, life was actually pretty clear -- t=
he monolith was the SCIM server (the source of truth), and the new Identity S=
ervice was the SCIM client.  Creating the initial download mechanism was no b=
ig deal -- one humongous batch transfer (or done in pieces if need be) and t=
he Identity Service is up to date with the initial snapshot.  But what happe=
ns when:
>> User changes their name (or a bunch of other profile fields)?  Not securi=
ty sensitive, but definitely UI sensitive.  If they are part of the data tra=
nsferred from the SCIM server to the SCIM client, it's definitely relevant.
>> User logs on or logs off?  (Groan ... the monolith cared a lot about this=
, because it affects UI like "is this person currently logged in" ... even w=
orse, the monolith updated a field in the actual user database row, which tr=
iggered a gazillion "user change" events (originally internal to the monolit=
h) documenting a change that had no other impact than to change the last log=
ged in timestamp ... sigh ... performance ... sigh.)
>> User changes their password?  We probably could have absorbed that functi=
on, but would have required modifications to a bunch of apps out of my team'=
s purview, so we didn't.
>> For that matter, *any* change happens between when the snapshot was taken=
, and the Identity Service caught up.
>> Anyone who has ever tried this trick has most likely run into the same ki=
nds of issues -- how do you deal with incremental changes that need to be co=
mmunicated from the server to the client?  Some of those changes (passwords,=
 ACLs, account deactivations, etc) are very much time critical.
>>=20
>> Our team chose to try to use webhooks from the monolith (SCIM server) bac=
k to the Identity Service (SCIM client), totally out-of-band to anything def=
ined by SCIM.  This would have worked OK if the webhook technology was actua=
lly reliable and incorporated things like guaranteed forwarding of the chang=
e event messages.  It doesn't work very well, of course, when the Identity S=
ervice hasn't fully processed the initial snapshot yet but receives a realti=
me update from the monolith.  In retrospect, this approach was probably a mi=
stake -- a different messaging technology would have been better for a narro=
w point-to-point requirement like this, but would not have addressed all of t=
he issues.  And what about a more broad-based notification requirement?
>>=20
>> Could we have turned the whole thing around, and made the new Identity Se=
rvice the SCIM server, and the monolith the SCIM client?  I suppose, but it w=
ould have required the Identity Service to be involved in a gazillion things=
 that were not authentication or authorization related, and the need for som=
e sort of out-of-band "incremental change" event notifications would have re=
mained, just going in the other direction.
>>=20
>> For the SCIM specification, It's the "incremental change" thing that is t=
he hard nut to crack, IMHO.  But it's actually a bigger problem than that, e=
ndemic to any scenario where you are trying to tear apart a monolith.
>>=20
>> Craig McClanahan
>>=20
>>=20
>>=20
>> On Mon, Aug 23, 2021 at 4:30 PM Matt Peterson (mpeterso) <Matt.Peterson=3D=
40oneidentity.com@dmarc.ietf.org> wrote:
>>> Thanks for the clarification. =20
>>>=20
>>> "Client" and "Server" are as used dozens of times in the existing RFCs w=
hich makes these as useful in understanding the SCIM protocol as they are fo=
r understanding the HTTP protocol.  In a SCIM protocol exchange there is a t=
hing that provides a resource (the server) and a thing that makes a HTTP req=
uest (GET,POST,PUT,PATCH,DELETE) on the resource (the client). =20
>>>=20
>>> I think it would be helpful to try and use this generally accepted HTTP t=
erminology if we can -- especially when talking about this synchronization t=
opic. =20
>>>=20
>>> Management server <-- SCIM Client
>>> Application Server <-- SCIM Server
>>>=20
>>> With this clarification, seems to me like your Management Server is usin=
g SCIM to manage accounts on the Application Server, and that the Management=
 Server would benefit from having an up-to-date cache of accounts that are o=
n the Application Server(s) even for cases where account changes/additions/d=
eletions are made "out of band"  (e.g. directly on the Application Server, n=
ot initiated by the Management server.)
>>>=20
>>> Did I understand correctly?
>>>=20
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: Danny Mayer <mayer@pdmconsulting.net>=20
>>> Sent: Friday, August 20, 2021 8:54 AM
>>> To: Matt Peterson (mpeterso) <Matt.Peterson@oneidentity.com>; SCIM WG <s=
cim@ietf.org>
>>> Subject: Re: [scim] SCIM Synchronization Problem
>>>=20
>>> CAUTION: This email originated from outside of the organization. Do not f=
ollow guidance, click links, or open attachments unless you recognize the se=
nder and know the content is safe.
>>>=20
>>>=20
>>> I decided to avoid the client/server naming convention because I find it=
 confusing. The system responsible for managing the user accounts and groups=
 I have declared to be the Management server. I believe you describe this as=
 the "SCIM Client" and is used to GET/POST/PATCH, etc.
>>> to the Application server to maintain the user accounts and groups. The a=
pplication server is what I believe you call the "SCIM Server". This provide=
s the SCIM API's needed.
>>>=20
>>> I find the use of client/server not helpful to understand their role in t=
he protocol.
>>>=20
>>> Danny
>>>=20
>>> On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:
>>> > Danny,
>>> >
>>> > To help me understand in your post is the "SCIM Client" and what is th=
e "SCIM Server" can you tell me which of your components (the Management Ser=
ver or the Application Server) implements SCIM endpoints?
>>> >
>>> > The component that acts as a "SCIM Server" is the component that provi=
des the of WebAPI endpoints that conform to the SCIM spec.  For example, the=
  /user, /group SCIM endpoints.
>>> >
>>> > The component(s) that uses these endpoints to query (GET)  users/group=
s or to create (POST) user/groups is the "SCIM client".
>>> >
>>> > --
>>> > Matt
>>> >
>>> > -----Original Message-----
>>> > From: scim <scim-bounces@ietf.org> On Behalf Of Danny Mayer
>>> > Sent: Wednesday, August 18, 2021 8:34 AM
>>> > To: SCIM WG <scim@ietf.org>
>>> > Subject: [scim] SCIM Synchronization Problem
>>> >
>>> > CAUTION: This email originated from outside of the organization. Do no=
t follow guidance, click links, or open attachments unless you recognize the=
 sender and know the content is safe.
>>> >
>>> >
>>> > I decided that this needs it's own thread and not be part of the meeti=
ng minutes.
>>> >
>>> > I have had a great deal of experience dealing with the user account sy=
nchronization problem. Here's my view of the problems.
>>> >
>>> > I will be calling one system Management Server and the other system Ap=
plication Server. I found client/server labels confusing. The Management Ser=
ver is what I am defining to be the server that sends updates to add/update/=
remove users and groups to the Application server whose account, groups and a=
ccess permissions are being managed.
>>> >
>>> > First some definitions of user accounts. There are usually more than o=
ne of each of these:
>>> > 1. Builtin accounts
>>> > 2. Special-purpose accounts
>>> > 3. Employee
>>> > 4. Contractor
>>> > 5. Agent
>>> > 6. Customer
>>> >
>>> > There may be more.
>>> >
>>> > 1. Builtin accounts: These are accounts that applications have and the=
re may be more than one. There is always an admin account which can do anyth=
ing, for example the administrator account in Active Directory or a database=
 admin account. The application may have more accounts for other purposes.
>>> >
>>> > 2. Special-purpose accounts: These may be set up to provide access to o=
ther applications, for example a SCIM request to a SCIM REST API should be h=
andled by a special account which cannot be used to login via a UI interface=
 and only be able to perform certain functions. In addition there may be acc=
ounts set up to listen for topics or queues on a message queue among other p=
ossibilities. Keeping separate accounts like this are important for tracking=
 in logs and applications.
>>> >
>>> > 3. Employee: These are accounts that employees may login to the applic=
ation.
>>> >
>>> > 4. Contractors: These accounts that a contractor performing work for t=
he company may use to log into an application. Unlike Employee accounts thes=
e would have an expiration date.
>>> >
>>> > 5. Agent: Accounts like this are for external users who may need to ma=
nage information for their own customers. An example of this is an insurance=
 agent logging in to handle an insurance policy for their clients.
>>> >
>>> > 6. Customers: These are where the customers are using the application d=
irectly. For a bank it's likely to be millions of customers. The management p=
latform should not be involved in managing these accounts.
>>> >
>>> > Let's now look at a few example applications.
>>> >
>>> > 1. Helpdesk
>>> > All employees and contractors will need to be able to log into a helpd=
esk application and enter tickets. This means loading information about all e=
mployees and contractors. For a company with only 1000 employees that's mana=
geable. For a company with 100K employees, it's a bigger challenge.
>>> >
>>> > 2. Customer Support
>>> > Only employees or contractors in the department providing customer sup=
port need access plus a few other employees. In addition identified customer=
s may need accounts.
>>> >
>>> > 3. Expenses
>>> > Not all employees or contractors will be submitting expenses so it may=
 not be necessary to have accounts for all possible users. This is something=
 that the application owner needs to decide.
>>> >
>>> > Now let's look at logistics.
>>> >
>>> > Bulk load:
>>> > Each application will need an initial set of accounts set up and for s=
omething like a helpdesk this could involve load 1000-100,000 accounts.
>>> > The information needed could come from either the management server or=
 separately, say from an HR system. Many servers that I have encountered lim=
it the number of records to something like 1000, so the pagination requireme=
nt is needed for this. Even when dealing with a limited subset of employees o=
r contractors you can run into this need.
>>> >
>>> > Synchronization
>>> > An application that is bulk-loaded above may need to be synchronized t=
o the management server if the data did not come from the management server.=

>>> >
>>> > Change Management
>>> > This is really a synchronization issue as well. Changes happen all the=
 time and new employees/contractors need to be added, terminated ones remove=
d and updates happen all the time. The best way of dealing with this may be t=
o set up a message queue that each application can subscribe to and they can=
 take the needed action when it's convenient for that application. It's not t=
he only method but it's the one I found to be the most helpful. There are tw=
o ways of doing that: 1. send the complete user information for new accounts=
, send just the change for updating accounts, send the ID for terminated acc=
ounts along with some meta information. The other method which I have used i=
s just to send the ID and whether it's new, updated or terminated.
>>> >
>>> > I hope this is helpful to the discussion.
>>> >
>>> > Danny
>>> >
>>> >
>>> > _______________________________________________
>>> > scim mailing list
>>> > scim@ietf.org
>>> > https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fww=
w.
>>> > ietf.org%2Fmailman%2Flistinfo%2Fscim&amp;data=3D04%7C01%7CMatt.Peterso=
n%
>>> > 40oneidentity.com%7C93c364afa0274e3fb35b08d963ea643e%7C91c369b51c9e439=

>>> > c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpbGZsb3d=

>>> > 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C=

>>> > 3000&amp;sdata=3DBqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&am=
p;
>>> > reserved=3D0
>>> >
>>>=20
>>> _______________________________________________
>>> scim mailing list
>>> scim@ietf.org
>>> https://www.ietf.org/mailman/listinfo/scim
> _______________________________________________
> scim mailing list
> scim@ietf.org
> https://www.ietf.org/mailman/listinfo/scim

--Apple-Mail-755B77A8-4C45-41B4-964B-29940A439E17
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">So a requirement here is to indicate what s=
chema is of interest for sync. Any notification method needs to be filterabl=
e on at least schema-id and potentially specific attributes. Eg a receiver m=
ay only be interested in events related to roles.&nbsp;<div><br></div><div>T=
he also shows why pre-conditioned HEAD queries couldn=E2=80=99t be used. The=
se types of queries can ask: does this url exist? Has this resource changed s=
ince this etag or date. &nbsp;Obviously any change to content changes the ha=
sh and mod-dates.&nbsp;</div><div><br></div><div>Obviously one of the downsi=
des to attaching session information to the user resource is affecting chang=
e rates. Why not have separate session resources point to users? &nbsp;Their=
 change rate and lifecycle are much different than that of a user. A best pr=
actice would be to keep this data separate from the user.&nbsp;</div><div>IO=
W -&gt; how much do we need to accommodate in sync? &nbsp;Should we be havin=
g a separate session schema discussion?</div><div><br><div dir=3D"ltr">Phil<=
/div><div dir=3D"ltr"><br><blockquote type=3D"cite">On Aug 24, 2021, at 8:49=
 AM, Danny Mayer &lt;mayer@pdmconsulting.net&gt; wrote:<br><br></blockquote>=
</div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF
 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8"=
>
 =20
 =20
    <p>I've been there and done that. We were lucky enough to have a way
      to differentiate between someone logging in and out and when an
      update is made to something that the SCIM client cares about. We
      preferred to send a notification to a queue that something has
      changed for the specific ID and application and leave it up to the
      "SCIM client" to query the application for the given ID. This had
      to be a manual operation as the SCIM client had no way of reading
      the queue. The queue was necessary for compliance and audit
      purposes so it wasn't a waste.</p>
    <p>Danny<br>
    </p>
    <div class=3D"moz-cite-prefix">On 8/23/21 9:43 PM, Craig McClanahan
      wrote:<br>
    </div>
    <blockquote type=3D"cite" cite=3D"mid:CANgkmLBneyCYFK4Hn0CG4pXDKW5Nfm+Z7=
7dbnhqrGpotaM8EkQ@mail.gmail.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-=
8">
      <div dir=3D"ltr">
        <div dir=3D"ltr">Several years ago (early in the lifetime of the
          SCIM specification), I was involved in exactly this kind of
          situation.&nbsp; I was trying to extract the Identity portion of a=

          monolith out into a separate service.&nbsp; Naturally, as you'll
          see in lots of monoliths, the User database information was
          used for *lots* of things, not just authentication and
          authorization, so we couldn't just remove it from the
          monolith's database.
          <div><br>
          </div>
          <div>=46rom a SCIM terminology perspective, life was actually
            pretty clear -- the monolith was the SCIM server (the source
            of truth), and the new Identity Service was the SCIM
            client.&nbsp; Creating the initial download mechanism was no big=

            deal -- one humongous batch transfer (or done in pieces if
            need be) and the Identity Service is up to date with the
            initial snapshot.&nbsp; But what happens when:</div>
          <div>
            <ul>
              <li>User changes their name (or a bunch of other&nbsp;profile
                fields)?&nbsp; Not security sensitive, but definitely UI
                sensitive.&nbsp; If they are part of the data transferred
                from the SCIM server to the SCIM client, it's definitely
                relevant.</li>
              <li>User logs on or logs off?&nbsp; (Groan ... the monolith
                cared a lot about this, because it affects UI like "is
                this person currently logged in" ... even worse, the
                monolith updated a field in the actual user database
                row, which triggered a gazillion "user change" events
                (originally internal to the monolith) documenting a
                change that had no other impact than to change the last
                logged in timestamp ... sigh ... performance ... sigh.)</li>=

              <li>User changes their password?&nbsp; We probably could have
                absorbed that function, but would have required
                modifications to a bunch of apps out of my team's
                purview, so we didn't.</li>
              <li>For that matter, *any* change happens between when the
                snapshot was taken, and the Identity Service caught up.</li>=

            </ul>
            <div>Anyone who has ever tried this trick has most likely
              run into the same kinds of issues -- how do you deal with
              incremental changes that need to be communicated from the
              server to the client?&nbsp; Some of those changes (passwords,
              ACLs, account deactivations, etc) are very much time
              critical.</div>
          </div>
          <div><br>
          </div>
          <div>Our team chose to try to use webhooks from the monolith
            (SCIM server) back to the Identity Service (SCIM client),
            totally out-of-band to anything defined by SCIM.&nbsp; This woul=
d
            have worked OK if the webhook technology was actually
            reliable and incorporated things like guaranteed forwarding
            of the change event messages.&nbsp; It doesn't work very well, o=
f
            course, when the Identity Service hasn't fully processed the
            initial snapshot yet but receives a realtime&nbsp;update from th=
e
            monolith.&nbsp; In retrospect, this approach was probably a
            mistake -- a different messaging technology would have been
            better for a narrow point-to-point requirement like
            this,&nbsp;but would not have addressed&nbsp;all of the&nbsp;iss=
ues.&nbsp; And
            what about a more broad-based notification requirement?</div>
          <div><br>
          </div>
          <div>Could we have turned the whole thing around, and made the
            new Identity Service the SCIM server, and the monolith the
            SCIM client?&nbsp; I suppose, but it would have required the
            Identity Service to be involved in a gazillion things that
            were not authentication or authorization related, and the
            need for some sort of out-of-band "incremental change" event
            notifications would have remained, just going in the other
            direction.</div>
          <div><br>
          </div>
          <div>For the SCIM specification, It's the "incremental change"
            thing that is the hard nut to crack, IMHO.&nbsp; But it's
            actually a bigger problem than that, endemic to any scenario
            where you are trying to tear apart a monolith.</div>
          <div><br>
          </div>
          <div>Craig McClanahan</div>
          <div><br>
          </div>
          <div><br>
          </div>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Aug 23, 2021 at 4:30=

            PM Matt Peterson (mpeterso) &lt;Matt.Peterson=3D<a href=3D"mailt=
o:40oneidentity.com@dmarc.ietf.org" target=3D"_blank" moz-do-not-send=3D"tru=
e">40oneidentity.com@dmarc.ietf.org</a>&gt;
            wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">Thanks for the
            clarification.&nbsp; <br>
            <br>
            "Client" and "Server" are as used dozens of times in the
            existing RFCs which makes these as useful in understanding
            the SCIM protocol as they are for understanding the HTTP
            protocol.&nbsp; In a SCIM protocol exchange there is a thing tha=
t
            provides a resource (the server) and a thing that makes a
            HTTP request (GET,POST,PUT,PATCH,DELETE) on the resource
            (the client).&nbsp; <br>
            <br>
            I think it would be helpful to try and use this generally
            accepted HTTP terminology if we can -- especially when
            talking about this synchronization topic.&nbsp; <br>
            <br>
            Management server &lt;-- SCIM Client<br>
            Application Server &lt;-- SCIM Server<br>
            <br>
            With this clarification, seems to me like your Management
            Server is using SCIM to manage accounts on the Application
            Server, and that the Management Server would benefit from
            having an up-to-date cache of accounts that are on the
            Application Server(s) even for cases where account
            changes/additions/deletions are made "out of band"&nbsp; (e.g.
            directly on the Application Server, not initiated by the
            Management server.)<br>
            <br>
            Did I understand correctly?<br>
            <br>
            <br>
            <br>
            -----Original Message-----<br>
            From: Danny Mayer &lt;<a href=3D"mailto:mayer@pdmconsulting.net"=
 target=3D"_blank" moz-do-not-send=3D"true">mayer@pdmconsulting.net</a>&gt; <=
br>
            Sent: Friday, August 20, 2021 8:54 AM<br>
            To: Matt Peterson (mpeterso) &lt;<a href=3D"mailto:Matt.Peterson=
@oneidentity.com" target=3D"_blank" moz-do-not-send=3D"true">Matt.Peterson@o=
neidentity.com</a>&gt;;
            SCIM WG &lt;<a href=3D"mailto:scim@ietf.org" target=3D"_blank" m=
oz-do-not-send=3D"true">scim@ietf.org</a>&gt;<br>
            Subject: Re: [scim] SCIM Synchronization Problem<br>
            <br>
            CAUTION: This email originated from outside of the
            organization. Do not follow guidance, click links, or open
            attachments unless you recognize the sender and know the
            content is safe.<br>
            <br>
            <br>
            I decided to avoid the client/server naming convention
            because I find it confusing. The system responsible for
            managing the user accounts and groups I have declared to be
            the Management server. I believe you describe this as the
            "SCIM Client" and is used to GET/POST/PATCH, etc.<br>
            to the Application server to maintain the user accounts and
            groups. The application server is what I believe you call
            the "SCIM Server". This provides the SCIM API's needed.<br>
            <br>
            I find the use of client/server not helpful to understand
            their role in the protocol.<br>
            <br>
            Danny<br>
            <br>
            On 8/19/21 1:42 PM, Matt Peterson (mpeterso) wrote:<br>
            &gt; Danny,<br>
            &gt;<br>
            &gt; To help me understand in your post is the "SCIM Client"
            and what is the "SCIM Server" can you tell me which of your
            components (the Management Server or the Application Server)
            implements SCIM endpoints?<br>
            &gt;<br>
            &gt; The component that acts as a "SCIM Server" is the
            component that provides the of WebAPI endpoints that conform
            to the SCIM spec.&nbsp; For example, the&nbsp; /user, /group SCI=
M
            endpoints.<br>
            &gt;<br>
            &gt; The component(s) that uses these endpoints to query
            (GET)&nbsp; users/groups or to create (POST) user/groups is the
            "SCIM client".<br>
            &gt;<br>
            &gt; --<br>
            &gt; Matt<br>
            &gt;<br>
            &gt; -----Original Message-----<br>
            &gt; From: scim &lt;<a href=3D"mailto:scim-bounces@ietf.org" tar=
get=3D"_blank" moz-do-not-send=3D"true">scim-bounces@ietf.org</a>&gt;
            On Behalf Of Danny Mayer<br>
            &gt; Sent: Wednesday, August 18, 2021 8:34 AM<br>
            &gt; To: SCIM WG &lt;<a href=3D"mailto:scim@ietf.org" target=3D"=
_blank" moz-do-not-send=3D"true">scim@ietf.org</a>&gt;<br>
            &gt; Subject: [scim] SCIM Synchronization Problem<br>
            &gt;<br>
            &gt; CAUTION: This email originated from outside of the
            organization. Do not follow guidance, click links, or open
            attachments unless you recognize the sender and know the
            content is safe.<br>
            &gt;<br>
            &gt;<br>
            &gt; I decided that this needs it's own thread and not be
            part of the meeting minutes.<br>
            &gt;<br>
            &gt; I have had a great deal of experience dealing with the
            user account synchronization problem. Here's my view of the
            problems.<br>
            &gt;<br>
            &gt; I will be calling one system Management Server and the
            other system Application Server. I found client/server
            labels confusing. The Management Server is what I am
            defining to be the server that sends updates to
            add/update/remove users and groups to the Application server
            whose account, groups and access permissions are being
            managed.<br>
            &gt;<br>
            &gt; First some definitions of user accounts. There are
            usually more than one of each of these:<br>
            &gt; 1. Builtin accounts<br>
            &gt; 2. Special-purpose accounts<br>
            &gt; 3. Employee<br>
            &gt; 4. Contractor<br>
            &gt; 5. Agent<br>
            &gt; 6. Customer<br>
            &gt;<br>
            &gt; There may be more.<br>
            &gt;<br>
            &gt; 1. Builtin accounts: These are accounts that
            applications have and there may be more than one. There is
            always an admin account which can do anything, for example
            the administrator account in Active Directory or a database
            admin account. The application may have more accounts for
            other purposes.<br>
            &gt;<br>
            &gt; 2. Special-purpose accounts: These may be set up to
            provide access to other applications, for example a SCIM
            request to a SCIM REST API should be handled by a special
            account which cannot be used to login via a UI interface and
            only be able to perform certain functions. In addition there
            may be accounts set up to listen for topics or queues on a
            message queue among other possibilities. Keeping separate
            accounts like this are important for tracking in logs and
            applications.<br>
            &gt;<br>
            &gt; 3. Employee: These are accounts that employees may
            login to the application.<br>
            &gt;<br>
            &gt; 4. Contractors: These accounts that a contractor
            performing work for the company may use to log into an
            application. Unlike Employee accounts these would have an
            expiration date.<br>
            &gt;<br>
            &gt; 5. Agent: Accounts like this are for external users who
            may need to manage information for their own customers. An
            example of this is an insurance agent logging in to handle
            an insurance policy for their clients.<br>
            &gt;<br>
            &gt; 6. Customers: These are where the customers are using
            the application directly. For a bank it's likely to be
            millions of customers. The management platform should not be
            involved in managing these accounts.<br>
            &gt;<br>
            &gt; Let's now look at a few example applications.<br>
            &gt;<br>
            &gt; 1. Helpdesk<br>
            &gt; All employees and contractors will need to be able to
            log into a helpdesk application and enter tickets. This
            means loading information about all employees and
            contractors. For a company with only 1000 employees that's
            manageable. For a company with 100K employees, it's a bigger
            challenge.<br>
            &gt;<br>
            &gt; 2. Customer Support<br>
            &gt; Only employees or contractors in the department
            providing customer support need access plus a few other
            employees. In addition identified customers may need
            accounts.<br>
            &gt;<br>
            &gt; 3. Expenses<br>
            &gt; Not all employees or contractors will be submitting
            expenses so it may not be necessary to have accounts for all
            possible users. This is something that the application owner
            needs to decide.<br>
            &gt;<br>
            &gt; Now let's look at logistics.<br>
            &gt;<br>
            &gt; Bulk load:<br>
            &gt; Each application will need an initial set of accounts
            set up and for something like a helpdesk this could involve
            load 1000-100,000 accounts.<br>
            &gt; The information needed could come from either the
            management server or separately, say from an HR system. Many
            servers that I have encountered limit the number of records
            to something like 1000, so the pagination requirement is
            needed for this. Even when dealing with a limited subset of
            employees or contractors you can run into this need.<br>
            &gt;<br>
            &gt; Synchronization<br>
            &gt; An application that is bulk-loaded above may need to be
            synchronized to the management server if the data did not
            come from the management server.<br>
            &gt;<br>
            &gt; Change Management<br>
            &gt; This is really a synchronization issue as well. Changes
            happen all the time and new employees/contractors need to be
            added, terminated ones removed and updates happen all the
            time. The best way of dealing with this may be to set up a
            message queue that each application can subscribe to and
            they can take the needed action when it's convenient for
            that application. It's not the only method but it's the one
            I found to be the most helpful. There are two ways of doing
            that: 1. send the complete user information for new
            accounts, send just the change for updating accounts, send
            the ID for terminated accounts along with some meta
            information. The other method which I have used is just to
            send the ID and whether it's new, updated or terminated.<br>
            &gt;<br>
            &gt; I hope this is helpful to the discussion.<br>
            &gt;<br>
            &gt; Danny<br>
            &gt;<br>
            &gt;<br>
            &gt; _______________________________________________<br>
            &gt; scim mailing list<br>
            &gt; <a href=3D"mailto:scim@ietf.org" target=3D"_blank" moz-do-n=
ot-send=3D"true">scim@ietf.org</a><br>
            &gt; <a href=3D"https://nam12.safelinks.protection.outlook.com/?=
url=3Dhttps%3A%2F%2Fwww" rel=3D"noreferrer" target=3D"_blank" moz-do-not-sen=
d=3D"true">https://nam12.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%=
2Fwww</a>.<br>
            &gt; <a href=3D"http://ietf.org" rel=3D"noreferrer" target=3D"_b=
lank" moz-do-not-send=3D"true">ietf.org</a>%2Fmailman%2Flistinfo%2Fscim&amp;=
amp;data=3D04%7C01%7CMatt.Peterson%<br>
            &gt; <a href=3D"http://40oneidentity.com" rel=3D"noreferrer" tar=
get=3D"_blank" moz-do-not-send=3D"true">40oneidentity.com</a>%7C93c364afa027=
4e3fb35b08d963ea643e%7C91c369b51c9e439<br>
            &gt;
            c989c1867ec606603%7C0%7C1%7C637650680638761908%7CUnknown%7CTWFpb=
GZsb3d<br>
            &gt;
            8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0=
%3D%7C<br>
            &gt;
3000&amp;amp;sdata=3DBqZusI4HsTB%2FyPo9SCrTMW6ZdIQNyVrPxGG%2BiiXx2fs%3D&amp;=
amp;<br>
            &gt; reserved=3D0<br>
            &gt;<br>
            <br>
            _______________________________________________<br>
            scim mailing list<br>
            <a href=3D"mailto:scim@ietf.org" target=3D"_blank" moz-do-not-se=
nd=3D"true">scim@ietf.org</a><br>
            <a href=3D"https://www.ietf.org/mailman/listinfo/scim" rel=3D"no=
referrer" target=3D"_blank" moz-do-not-send=3D"true">https://www.ietf.org/ma=
ilman/listinfo/scim</a><br>
          </blockquote>
        </div>
      </div>
    </blockquote>
 =20

<span>_______________________________________________</span><br><span>scim m=
ailing list</span><br><span>scim@ietf.org</span><br><span>https://www.ietf.o=
rg/mailman/listinfo/scim</span><br></div></blockquote></div></body></html>=

--Apple-Mail-755B77A8-4C45-41B4-964B-29940A439E17--

