From nobody Thu Oct 1 06:29:53 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 292873A1052 for ; Thu, 1 Oct 2020 06:29:51 -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 oeRklWdlUEMU for ; Thu, 1 Oct 2020 06:29:49 -0700 (PDT) Received: from mail-vs1-xe42.google.com (mail-vs1-xe42.google.com [IPv6:2607:f8b0:4864:20::e42]) (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 2F2BF3A0967 for ; Thu, 1 Oct 2020 06:29:49 -0700 (PDT) Received: by mail-vs1-xe42.google.com with SMTP id 7so2563608vsp.6 for ; Thu, 01 Oct 2020 06:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=xHMw5RvjcgtNBixP01G1A0QeekE1y2aebls9L16JWwY=; b=n72m6SNRWMmVZC9Vhc64Mzsp8LNrlMWiiXY02uwAc1p4oQxQiKWwLHVRkv8/svEkU1 QQcxuhPO93UpjVzHVVwBIqesRwl2SnSDgDlSIBIR5xaKSJEmmmLMNQx7w6zSrzDxCF54 5Km8TMB02C9CU1KIaS8sARSE7AYqt1Uql0fcTKJPoXzzzXMFA2jHKtw6aa6767tzB1UR ihCPi3fSbBBgMHO/KiQF+I2qeQ8k8RPkuO3RiZ9YeZ4MzY2mVhEJ2UXTs8L5hZhLBJDH T72reXIQzE576F1rPgaahmBCHlBgVNpsKUJpFBgZJvZBV2SQOLWF4FBkomATBgJn7S5U t0MQ== 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; bh=xHMw5RvjcgtNBixP01G1A0QeekE1y2aebls9L16JWwY=; b=V9NJeko8RbCIRCzW3BRYraxaUn7kthAzvGtZnI8BP5WXdtATxRXeGVnptU7KC3XDwN 7tmzV3sjkhO6sNkmAOnmfw7JQ7oHdd4lcRkyEQ/a0DCpjUHB/8hcWZ0Zm67P8HgFbSse UD9fZ/J/T14tsxDZZLHfdK/y/oKD+Hb9Fb4I7GiYBm5tJVr6DkSuuH99mQiZYrA3Fyup gKPtb5egjd5dpAOuKTCFB0LvCcPFNWrNgp50mCSdtgABJzpOrnnBnefU9mVEHOWc+7YF qsXBPHbNtkUtI8/iZVmUZl9JwxMIsqb6Dxx/oz6WLMIWmj2NEFL/GRbzZU11DQsRHeYh bdQw== X-Gm-Message-State: AOAM533RrOiK5x2i8Yi3GE6VyuyMb1Td1T0qdlcosdb4+3f9+5X0vdA6 3WoNCwOQ5El8iUjU6E+EeKh/PxmkE2ZpWELVnRBUwohC7LL+Mw== X-Google-Smtp-Source: ABdhPJzEuDQzgS20xFS4MmbqqfxAuZbOQnNUQtF2ZY9iW8s4bbXS/8MEu6QGEc8QWafYYSWEgHdAKGhz9b257lc30nI= X-Received: by 2002:a67:e981:: with SMTP id b1mr4998620vso.43.1601558988247; Thu, 01 Oct 2020 06:29:48 -0700 (PDT) MIME-Version: 1.0 References: <89C877BA-9DF9-44A1-A1A9-5719D3665B76@amazon.com> In-Reply-To: From: Shelley Date: Thu, 1 Oct 2020 08:29:36 -0500 Message-ID: To: Phillip Hunt , "McAdams, Darin" , "scim@ietf.org" Content-Type: multipart/alternative; boundary="00000000000094d9ce05b09c02c0" Archived-At: Subject: Re: [scim] PATCH Multi-Valued Attribute Value Type X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2020 13:29:51 -0000 --00000000000094d9ce05b09c02c0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the clarification. Should the "add" descriptions [1] be corrected to account for arrays and other literals being provided? Current text: > The value MAY be a quoted value, or it may be a JSON object containing= the sub-attributes of the complex attribute specified in the operation's "= path". > > Should it instead be something more like the following? > The value MUST contain a value with the data type of the attribute spe= cified in the operation's "path". > > (And, similar clarifications for "replace" would be useful, too, with the additional clarification that CMVA value paths must replace with only a single element value, and may not provide an array.) [1] https://tools.ietf.org/html/rfc7644#section-3.5.2.1 On Wed, Sep 30, 2020 at 8:25 PM Phillip Hunt wrote: > If the path is a simple attribute than the patch value is the actual > simple assignment. > > If the path is a complex attribute than Patch value is the set of > attributes that constitute a value. > > CMVA then follows that value is an array unless a [value path filter] was > specified. > > The idea is that path can be either fine-grained or point to a whole > object much like in the json patch spec. The big difference is scim uses = a > filter for multivalue arrays over indexing. Thus value of =E2=80=9Cvalue= =E2=80=9D depends > on what path points to. > > Phil > > On Sep 30, 2020, at 3:39 PM, McAdams, Darin 40amazon.com@dmarc.ietf.org> wrote: > > =EF=BB=BF > > I=E2=80=99m curious as well. We are proposing a SCIM interop profile in F= astFed > and now I=E2=80=99m hoping we got it right! > > https://openid.net/specs/fastfed-scim-1_0-02.html#rfc.section.4.3.7 > > > > *From: *scim on behalf of Shelley < > randomshelley@gmail.com> > *Date: *Wednesday, September 30, 2020 at 2:23 PM > *To: *"scim@ietf.org" > *Subject: *[EXTERNAL] [scim] PATCH Multi-Valued Attribute Value Type > > > > For "add" and "replace" PATCH operations that specify multi-valued > attributes, is the content of the "*value*" attribute supposed to be an *= array > *containing the new/replaced element(s) or a single *JSON object * > containing the new/replaced element? The RFC seems to contain examples fo= r > both, and I would like to better understand the difference. > > > > *Add Operation "Value" Type for Multi-Valued Attributes* > > There is an "*add*" example on page 37 which specifies an *array *for a > multi-valued attribute: > > { > "op": "add", > "path": "members", > "value": *[*{ > "display": "Babs Jensen", > "$ref": "https://example.com/v2/Users/2819c223...413861904646", > "value": "2819c223-7f76-453a-919d-413861904646" > }*]* > } > > > > The description of "add", however, indicates that it contains "*a "value" > member whose content specifies the value to be added.*" In the case of > "add", the value being added is the individual element, not an array. > > > > Also, the "add" description indicates that the "*value MAY be a quoted > value, or it may be a JSON object containing the sub-attributes*" but > does *not *seem to allow arrays (nor JSON literals, such as booleans or > numbers, which is a separate question...). > > > > *Is the description or the example incorrect? Should the operation "value= " > here be a JSON object or an array?* > > > > *Replace Operation "Value" Type for Multi-Valued Attributes * > > For "*replace*", there is an example on page 44 that specifies an *array = *for > the "value" of a multi-valued attribute: > > { > "op": "replace", > "path": "members", > "value": *[*{ > "display": "Babs Jensen", > "$ref": "https://example.com/v2/Users/2819c223...413861904646", > "value": "2819c223...413861904646" > }, > { > "display": "James Smith", > "$ref": "https://example.com/v2/Users/08e1d05d...473d93df9210", > "value": "08e1d05d...473d93df9210" > } > *]* > } > > However, there is also a "*replace*" example on page 45 that specifies an= *object > *(not an array) for the "value" of a multi-valued attribute: > > { > "op": "replace", > "path": "addresses[type eq \"work\"]", > "value": *{* > "type": "work", > "streetAddress": "911 Universal City Plaza", > "locality": "Hollywood", > "region": "CA", > "postalCode": "91608", > "country": "US", > "formatted": "911 Universal City Plaza\nHollywood, CA 91608 US", > "primary": true > *}* > } > > > The use of the array for "replace" on "members" seems appropriate since i= t > is replacing the entire attribute with one or more values. For the > "addresses" value path, it's a little less clear to me. The use of an > object seems to imply that even if multiple addresses are matched by the > filter, only one new element may be specified to take it's/their place. C= an > someone provide clarification on when to use *array vs. object *here? > > > > Thank you! > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim > > --00000000000094d9ce05b09c02c0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the clarification.

Should the "add" descriptions [1] be corrected to account for a= rrays and other literals being provided? Current text:
= 
   The value MAY be a quoted value, or it may be a JSON object containi=
ng the sub-attributes of the complex attribute specified in the operation&#=
39;s "path".
Should it instead be something more like the followin= g?
   The value MUST contain a value with=
 the data type of the attribute specified in the operation's "path=
".
(And, similar clarifications for "replace" would be us= eful, too, with the additional clarification that CMVA value paths must rep= lace with only a single element value, and may not provide an array.)
=

<= div>

On Wed, Sep 30, 2020 at 8:25 PM Phillip Hunt <phil.hunt@independentid.com> wr= ote:
If the path is a simple attribute than the patch value is the actual= simple assignment.=C2=A0

If the path is a complex attri= bute than Patch value is the set of attributes that constitute a value.=C2= =A0

CMVA then follows that value is an array unles= s a [value path filter] was specified.

The idea is= that path can be either fine-grained or point to a whole object much like = in the json patch spec. The big difference is scim uses a filter for multiv= alue arrays over indexing.=C2=A0 Thus value of =E2=80=9Cvalue=E2=80=9D depe= nds on what path points to.=C2=A0

Phil

On Sep 30, 2020, = at 3:39 PM, McAdams, Darin <darinm=3D40amazon.com@dmarc.ietf.org> wrote:
=EF=BB= =BF

I=E2=80=99m curious as well. We are proposing a SCIM= interop profile in FastFed and now I=E2=80=99m hoping we got it right!<= /u>

https://openid.net/specs/fast= fed-scim-1_0-02.html#rfc.section.4.3.7

=C2=A0

From: = scim <scim-bounces@ietf.org>= ; on behalf of Shelley <randomshelley@gmail.com>
Date: Wednesday, September 30, 2020 at 2:23 PM
To: "scim@ie= tf.org" <sci= m@ietf.org>
Subject: [EXTERNAL] [scim] PATCH Multi-Valued Attribute Value Type

=C2=A0

For "add" and "replace" PATCH op= erations that specify multi-valued attributes, is the content of the "= value" attribute supposed to be an array containing the new/replaced element(s) or a single JSON obj= ect containing the new/replaced element? The RFC seems to contain examples for = both, and I would like to better understand the difference.

=C2=A0

Add Operation "Value" Type for Multi= -Valued Attributes

There is an "add" example on page 3= 7 which specifies an array for a multi-valued attribute:

= {
=C2=A0 "op": = "add",
=C2=A0 "path"= : "members",
=C2=A0 "value"= ;: [{
=C2=A0 =C2=A0 "dis= play": "Babs Jensen",
=C2=A0 =C2=A0 "$re= f": "https://example.com/v2/Users/2819c223...413861904646= ",
=C2=A0 =C2=A0 "val= ue": "2819c223-7f76-453a-919d-413861904646"
=C2=A0 }]=
}<= /p>

=C2=A0

The description of "add", however, indicat= es that it contains "a "value" member whose content speci= fies the value to be added." In the case of "add"= , the value being added is the individual element, not an array.<= /u>

=C2=A0

Also, the "add" description indicates that= the "value MAY be a quoted value, or it may be a JSON object containing the sub-at= tributes" but does not seem to allow arrays (nor JSON literals, such as booleans or num= bers, which is a separate question...).

=C2=A0

Is the description or the example incorrect? Shou= ld the operation "value" here be a JSON object or an array?

=C2=A0

Replace Operation "Value" Type for M= ulti-Valued Attributes

For "replace", there is an example = on page 44 that specifies an array for the "value" of a multi-valued attribute: =

= {
=C2=A0 "op": "replace",
=C2=A0 "path": "members",
=C2=A0 "value": [{
=C2=A0 =C2=A0 =C2=A0 "display": "Babs Jensen",
=C2=A0 =C2=A0 =C2=A0 "$ref": "https://example.com/v2= /Users/2819c223...413861904646",
=C2=A0 =C2=A0 =C2=A0 "value": "2819c223...413861904646"=
=C2=A0 =C2=A0 },
=C2=A0 =C2=A0 {
=C2=A0 =C2=A0 =C2=A0 "display": "James Smith",
=C2=A0 =C2=A0 =C2=A0 "$ref": "https://example.com/v2= /Users/08e1d05d...473d93df9210",
=C2=A0 =C2=A0 =C2=A0 "value": "08e1d05d...473d93df9210"=
=C2=A0 =C2=A0 }
=C2=A0 ]
}

However, there is also a "replace" = example on page 45 that specifies an object (not an array) for the "value" of a multi-valued at= tribute:

= {
=C2=A0 "op": "replace",
=C2=A0 "path": "addresses[type eq \"work\"]",=
=C2=A0 "value": {
=C2=A0 =C2=A0 "type": "work",
=C2=A0 =C2=A0 "streetAddress": "911 Universal City Plaza&quo= t;,
=C2=A0 =C2=A0 "locality": "Hollywood",
=C2=A0 =C2=A0 "region": "CA",
=C2=A0 =C2=A0 "postalCode": "91608",
=C2=A0 =C2=A0 "country": "US",
=C2=A0 =C2=A0 "formatted": "911 Universal City Plaza\nHollyw= ood, CA 91608 US",
=C2=A0 =C2=A0 "primary": true
=C2=A0 }
}


The use of the array for "replace" on "members" seems a= ppropriate since it is replacing the entire attribute with one or more valu= es. For the "addresses" value path, it's a little less clear = to me. The use of an object seems to imply that even if multiple addresses are matched by the filter, only one new element may be specified to take i= t's/their place. Can someone provide clarification on when to use array vs. object here?

=C2=A0

Thank you!

_______________________________________________
scim = mailing list
scim@ietf.org
https://www.ietf.org/mailman/listinfo/= scim
--00000000000094d9ce05b09c02c0-- From nobody Thu Oct 1 10:51:40 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C4E3A1193 for ; Thu, 1 Oct 2020 10:51:39 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 hcj_3Dl-EXJt for ; Thu, 1 Oct 2020 10:51:38 -0700 (PDT) Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com [IPv6:2607:f8b0:4864:20::a2a]) (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 0BF533A1191 for ; Thu, 1 Oct 2020 10:51:37 -0700 (PDT) Received: by mail-vk1-xa2a.google.com with SMTP id q124so1188891vkb.8 for ; Thu, 01 Oct 2020 10:51:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=4s02Sxxp9R7Q64QQoztBbdsuuGXSljZN6YOKtyDeXC4=; b=Rc2CqMi8canrOHxbsjZI+yEC8yxTA2jYwqdHA+l6SEs6gg31+XXzI1kFjFt0GbLZSI utXWtB5qfDjYC7/IFOONpfCFfwnEJzoYsvQO1v//1JWQgtCmyg7JBzeE2uzn3fJFFX4J dmHiYi3Y3zPy1YOSopQxBeOmMs4ZtzDkvvkoMr94kDKwRcEaaEC8b2nt2Caiat9CEp+8 hUQ/KXucX1D22MUWI6A8ZBeaDavnwvB2bSBFM90fg5Z2HCrIFW+wQgcNi6XyElZTGR2C jPT36oF+3V6Was0UWzihoaqZcIYNNnVWVUoz5md3UjdL3Kn8fBTfIhFTKM8H9PHBEECZ 3QKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=4s02Sxxp9R7Q64QQoztBbdsuuGXSljZN6YOKtyDeXC4=; b=L8FW9djIZL/DNhLCUWp4mpf0wwIW6GGYLU5mp0J7UwCMnD0d50OlMXSgOR8XjxevHT 7Mphd5Ts30/qKbLYrBubhoMWXh77Fsx8R5X7lGuolp80Rb94//2dYncMOTA8ibC1ArwO arNlOM5chXfUp8MYmagNf1PYgpvZr9vRAu7GUERB+08hTLge9/YQRsQJrhWoUMfRJ6+K 6uuIqJQvDSFxMtx0RaIDzMnOwbgJvYNWelkA6YLX2UL+GONx9VSKIudbgnxuYOF4blg+ RrWTeeE+trb7K8aSIXOq7oSarnxdaQPNPvphYsha7zAnq1x92M96cZ1ggqNOf1yyxFGe CA0w== X-Gm-Message-State: AOAM532cVWewNJB0FwrGpp+wC9AGaJGnkPxxu0AD7kBpiMz2uR1TT2YY 2Cf2avdKn2GPscaqBNrsUwXco0whts4DIQIPsB5tDOigoSI4Ew== X-Google-Smtp-Source: ABdhPJzMiE1K1F5xCrUzQoIAqAJsg7yWzBpA9VYkoNwODmzpxUMz6j0rOLGzSWcQdD0NxtIX57tkaLSOwiccKbJd6EE= X-Received: by 2002:a05:6122:6bb:: with SMTP id r27mr5839311vkq.3.1601574696574; Thu, 01 Oct 2020 10:51:36 -0700 (PDT) MIME-Version: 1.0 From: Shelley Date: Thu, 1 Oct 2020 12:51:25 -0500 Message-ID: To: scim@ietf.org Content-Type: multipart/alternative; boundary="000000000000dee3ef05b09faa48" Archived-At: Subject: [scim] PATCH "Add" Operation with Value Paths X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2020 17:51:39 -0000 --000000000000dee3ef05b09faa48 Content-Type: text/plain; charset="UTF-8" What is the expected behavior when an "*add*" operation provides a "*path*" containing a multi-valued attribute with a *value filter*? In this example, I suppose that any emails that meet the criteria should set/replace their "type" sub-attribute? (Although, I'm not sure why a consumer would choose "add" vs. "replace".) { "op": "add", "path": "emails[primary eq false].type", "value": "other" } In this example, however, I'm not at all sure of the semantic meaning of the filter? Should this be unsupported (resulting in a failure), should the filter itself effectively be ignored (where the enclosed email element is just appended to the emails array as if the filter was not provided), or should this have some other behavior (e.g. some type of attribute merging for elements that match the filter)? { "op": "add", "path": "emails[primary eq false]", "value": ... } --000000000000dee3ef05b09faa48 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What is the expected behavior when an "add&quo= t; operation provides a "path" containing a multi-valued a= ttribute with a value filter?

In this example, I suppose that= any emails that meet the criteria should set/replace their "type"= ; sub-attribute? (Although, I'm not sure why a consumer would choose &q= uot;add" vs. "replace".)
= {
=C2=A0 =C2=A0 "op": "add",
=C2=A0 =C2=A0 "path": "emai= ls[primary eq false].type",
=C2=A0 =C2=A0 "value": "other"
}

In this example= , however, I'm not at all sure of the semantic meaning of the filter? S= hould this be unsupported (resulting in a failure), should the filter itsel= f effectively be ignored (where the enclosed email element is just appended= to the emails array as if the filter was not provided), or should this hav= e some other behavior (e.g. some type of attribute merging for elements tha= t match the filter)?
{
=C2=A0 =C2=A0 "op": "add",
= =C2=A0 =C2=A0 "path": "emails[primary eq false]",
= =C2=A0 =C2=A0 "value": ...
}
--000000000000dee3ef05b09faa48-- From nobody Thu Oct 1 11:29:26 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2753A0AAB for ; Thu, 1 Oct 2020 11:29:24 -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=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 v9UMq8-CtoY5 for ; Thu, 1 Oct 2020 11:29:22 -0700 (PDT) Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0: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 B4C523A0AA4 for ; Thu, 1 Oct 2020 11:29:22 -0700 (PDT) Received: by mail-pg1-x534.google.com with SMTP id 7so4669211pgm.11 for ; Thu, 01 Oct 2020 11:29:22 -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=j80WjPB2soDAZ0j6OTW4AqVZ/m3QiEfSifIcMLHAnI8=; b=JtBOgzipTv9q74nWklBD6Pvwx6GxRcEByMtmD+/bvqpYv9FX2kfzvNAY9eDgn2b6xD 5XFzPS9OOsONr+c6zW8IahApYJPddiXiw7vmjqdhWuKnTkHrLcgZcibu/1r0I/J2NmoJ BT58aG67zhQbpTLHDXyhzAA9z+pKph2y9fxipLut4iCeMmOeX/4/0O9S8A/SgWmyCUca t4KLUP62UmJkdo5vo59GOXVbg9t+g8WCDxwqzquhnEGQ+zBFmeGJ1vF3cZ+NRp1xtjJp P6qb6KcwR6xiPAtCkPRzEr7SZo+g90igWQ9TW1Um6KzZPLgP+iW369bXayhycmppXxlV hkTQ== 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=j80WjPB2soDAZ0j6OTW4AqVZ/m3QiEfSifIcMLHAnI8=; b=B2mhfICWhQh342lJLPPvKDt8RWtKZ2m8daEcRud1/ApNpIb9W8HcJPn7jNPSs/mvFz 9gYh3fxxBzeaQf6i2OEOErw1/T+kiTZtLE8FQjh+xsHLgibgBRjXOvsH1SgisHQp6eKC kn5YvmYbOGWxYqbGSgR2pErkywIV6Dr5RGowoccUWEKvDSyi7QZriL7nsvvHuGIxgUI2 jvdRqBML5xP8jiTxIJjovC1zQVh5+aAj1lT6ElFORl1z3E1qeYOVeI8UtoLvOjNW8TTw w3Vb9ishRHZpLScGIiy0RgPqzrhzfB+eJBmURF10uV0rGdE69IiIu8fgIzitOZsNp6Wz 8GnQ== X-Gm-Message-State: AOAM532OzjQddmCAnxR/YWgbTxCOXlMSr42xgDZx75yxQgZ/7J+MAffs yg3UELJqywBT6nKS5+iG6KTflqKV5xoXUwzt X-Google-Smtp-Source: ABdhPJxLZwCxpIIimEYdRf3aCh/kVWIIhVTTA9iQrFNnDOqmj7fF4c8D2ryckM3SeDUghgBUAiGGBQ== X-Received: by 2002:a62:7bc7:0:b029:138:9430:544e with SMTP id w190-20020a627bc70000b02901389430544emr8743700pfc.1.1601576961811; Thu, 01 Oct 2020 11:29:21 -0700 (PDT) Received: from ?IPv6:2001:569:79bc:100:7ddc:cecb:f0cf:48fd? (node-1w7jr9qqo6k577mpwjkl9cvst.ipv6.telus.net. [2001:569:79bc:100:7ddc:cecb:f0cf:48fd]) by smtp.gmail.com with ESMTPSA id o1sm193173pgi.41.2020.10.01.11.29.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Oct 2020 11:29:21 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-7C02EC71-C85A-44AD-BE20-A5C6910B8738 Content-Transfer-Encoding: 7bit From: Phillip Hunt Mime-Version: 1.0 (1.0) Date: Thu, 1 Oct 2020 11:29:20 -0700 Message-Id: <4E089711-D235-4709-A10E-1606902E2F73@independentid.com> References: Cc: scim@ietf.org In-Reply-To: To: Shelley X-Mailer: iPhone Mail (17H35) Archived-At: Subject: Re: [scim] PATCH "Add" Operation with Value Paths X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Oct 2020 18:29:24 -0000 --Apple-Mail-7C02EC71-C85A-44AD-BE20-A5C6910B8738 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Using add instead of replace would not be expected. So an add with a valuep= ath filter to a mv attribute would not make sense. An add of a sub-attribut= e using a valuepath filter would. For many implementations you could expect= a bad request response.=20 As past editor I find it hard to agree it is necessary to document every une= xpected behavior (There are 1000s). I caution the members of this list that s= cim receives significant criticism for *over* specification. =20 Still for implementers, I always suggest using =E2=80=9Crobust=E2=80=9D codi= ng approach which means that if you feel you can clearly understand the requ= est you are free to accept it. Still, likewise clients should be prepared t= o accept bad request.=20 Phil > On Oct 1, 2020, at 10:51 AM, Shelley wrote: >=20 > =EF=BB=BF > What is the expected behavior when an "add" operation provides a "path" co= ntaining a multi-valued attribute with a value filter? >=20 > In this example, I suppose that any emails that meet the criteria should s= et/replace their "type" sub-attribute? (Although, I'm not sure why a consume= r would choose "add" vs. "replace".) > { > "op": "add", > "path": "emails[primary eq false].type", > "value": "other" > } >=20 > In this example, however, I'm not at all sure of the semantic meaning of t= he filter? Should this be unsupported (resulting in a failure), should the f= ilter itself effectively be ignored (where the enclosed email element is jus= t appended to the emails array as if the filter was not provided), or should= this have some other behavior (e.g. some type of attribute merging for elem= ents that match the filter)? > { > "op": "add", > "path": "emails[primary eq false]", > "value": ... > } > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim --Apple-Mail-7C02EC71-C85A-44AD-BE20-A5C6910B8738 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Using add instead of replace would not be e= xpected.  So an add with a valuepath filter to a mv attribute would not= make sense.  An add of a sub-attribute using a valuepath filter would.=  For many implementations you could expect a bad request response.&nbs= p;

As past editor I find it hard to agree it is necessary= to document every unexpected behavior (There are 1000s). I caution the memb= ers of this list that scim receives significant criticism for *over* specifi= cation.  

Still for implementers, I always sug= gest using =E2=80=9Crobust=E2=80=9D coding approach which means that if you f= eel you can clearly understand the request you are free to accept it.  = Still, likewise clients should be prepared to accept bad request. 

Phil

On Oct 1, 2020, at 10:51 AM, Shelley <randomshelley@gmail.com> w= rote:

=EF= =BB=BF
What is the expected behavior when an "add" op= eration provides a "path" containing a multi-valued attribute with a <= b>value filter?

In this example, I suppose that any emails that m= eet the criteria should set/replace their "type" sub-attribute? (Although, I= 'm not sure why a consumer would choose "add" vs. "replace".)
{
    "op": "add",
    "path": "emails[primary eq false= ].type",
    "valu= e": "other"
}

In this example, however, I'm not at all sure of the semantic m= eaning of the filter? Should this be unsupported (resulting in a failure), s= hould the filter itself effectively be ignored (where the enclosed email ele= ment is just appended to the emails array as if the filter was not provided)= , or should this have some other behavior (e.g. some type of attribute mergi= ng for elements that match the filter)?
<= span style=3D"font-family:monospace">{
    "op": "add",
&nbs= p;   "path": "emails[primary eq false]",
    "value": ...<= br>}
_______________________________________________
scim m= ailing list
scim@ietf.org
https://www.ietf.o= rg/mailman/listinfo/scim
= --Apple-Mail-7C02EC71-C85A-44AD-BE20-A5C6910B8738-- From nobody Tue Oct 6 09:40:17 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDC433A14D5 for ; Tue, 6 Oct 2020 09:40:10 -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, HTML_FONT_LOW_CONTRAST=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 (1024-bit key) header.d=slack-corp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id raEeXBI1aig6 for ; Tue, 6 Oct 2020 09:40:08 -0700 (PDT) Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 E4B3E3A14F2 for ; Tue, 6 Oct 2020 09:40:03 -0700 (PDT) Received: by mail-io1-xd32.google.com with SMTP id m17so13739130ioo.1 for ; Tue, 06 Oct 2020 09:40:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=slack-corp.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=BmHJ+6AFVjXxpo/UZwSJ+v+pJcN4lc6ZM2g3UZgXl0U=; b=nap5oF1XtUEyI1cPZAonSfkskho0Mi0y8Cst/yGQTY6dpXeYcBzHGLrfQoAtBn6Vrh jMRv0gJV5gDvQqtAuhtWZVuUltnHFh7KfSfWBlIIA8/MHduRPDgGckEpAvV27TeRRSV4 kCLTRTSjAiISt9DrM3ZRwPhnZRn/fZHWDuAf0= 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; bh=BmHJ+6AFVjXxpo/UZwSJ+v+pJcN4lc6ZM2g3UZgXl0U=; b=Y11ITogpmtNh4E1dZKOsaKOSeKC+6aPx4zzxW3erhfLkrq1mz2sWuJdXRGQwrZ1nah XGjXGaSy7I+4C9XL08VZ2eAC0em6C/jTDbJtwuHs+XlYLUNOoyxP31HYEFnuxz0D5g8j EJpqjzU2IRzN+Cg8w6ULUC0VPcCZgDvIf+G9G+BBGBCLbD9N7XGtOSjWclgbRWqg3nd2 3N4UcWcEFwP38RrjnizekI2ST7vWb4ZlqdpedNfnjWwuZgyHBP+10goa63xhwN1sQr6g D2z4zGg35ZLydNTey7l4gLBC7yiwIP6w5jITAKcbj2FODTkK44qPBIhllN8/G8s9NzrP 3H0Q== X-Gm-Message-State: AOAM530Sn6LtZPmE4M2HL6gOLfXoLexZxRn+g+uVzX7H7twMp9WRj7ws kc0hm8hlsSajays6WzFZrAYYP4/fMXa4kasG+cCLOT+3JJw= X-Google-Smtp-Source: ABdhPJxxmLlmy8XplHVdlmjtaKKfFu3Wl0GgbihYRTbWJP329jUXhwjCcE/60FHvqAlzo4CUY/rZfh717iRf/tjKbGw= X-Received: by 2002:a5e:8b0b:: with SMTP id g11mr1920888iok.140.1602002402456; Tue, 06 Oct 2020 09:40:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Audrei Drummond Date: Tue, 6 Oct 2020 12:39:51 -0400 Message-ID: To: scim@ietf.org Content-Type: multipart/mixed; boundary="000000000000211dd205b10340f9" Archived-At: Subject: Re: [scim] Who's interested in working on what? X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 16:40:16 -0000 --000000000000211dd205b10340f9 Content-Type: multipart/alternative; boundary="000000000000211dd005b10340f7" --000000000000211dd005b10340f7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm also interested in working on / contributing to 1 + 2 whenever that kicks off. On Wed, Sep 9, 2020 at 1:12 PM wrote: > > ---------- Forwarded message ---------- > From: Darran Rolls > To: "scim@ietf.org" > Cc: > Bcc: > Date: Wed, 9 Sep 2020 16:07:42 +0000 > Subject: [scim] Who's interested in working on what? > > Folks > > > > Attached is the tally of the responses I=E2=80=99ve received to date. Ho= pefully > there are lots of additions to be made, so I=E2=80=99m providing the resu= lts so > far. If you want to change/add your interest area, likely best to send > that back to be and I=E2=80=99ll continue to manage the document and prov= ide > relevant updates when requited (I=E2=80=99m assuming we don=E2=80=99t hav= e a doc repo until > the WG is reenacted=E2=80=A6) > > > > -- > > Darran Rolls > > https://www.darranrolls.com > > LinkedIn @djrolls > > > > > > > ---------- Forwarded message ---------- > From: Paul Logston > To: Darran Rolls > Cc: Paul Lanzi , Pamela Dingle 40microsoft.com@dmarc.ietf.org>, "scim@ietf.org" > Bcc: > Date: Wed, 9 Sep 2020 13:11:40 -0400 > Subject: Re: [scim] Moving towards the next IETF Meeting > +1 for interest > > Paul Logston > (510) 755 - 4474 > paul.logston@gmail.com > linkedin.com/in/paullogston > > > > On Wed, Sep 9, 2020 at 12:03 PM Darran Rolls wrote: > >> Me2. >> >> >> >> I=E2=80=99ve not shared the results of our =E2=80=9CI=E2=80=99m interest= ed to contribute here=E2=80=9D >> analysis =E2=80=93 I=E2=80=99ll do that now =E2=80=93 that=E2=80=99s a k= ey input into this process. In >> summary there are gaps but commonality and lots to do=E2=80=A6 >> >> >> >> Darran >> >> >> >> *From: *scim on behalf of Paul Lanzi < >> paul@remediant.com> >> *Date: *Wednesday, September 9, 2020 at 10:55 AM >> *To: *Pamela Dingle >> *Cc: *"scim@ietf.org" >> *Subject: *Re: [scim] Moving towards the next IETF Meeting >> >> >> >> Hi Pam - certainly would be interested. >> >> >> >> --Paul >> >> [image: Image removed by sender.]=E1=90=A7 >> >> >> >> On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle > 40microsoft.com@dmarc.ietf.org> wrote: >> >> Hi SCIM working group, >> >> >> >> I would like to propose we get together to do three things: >> >> >> >> 1) Share each of our goals for where SCIM can go >> >> >> >> 2) Find the commonalities >> >> >> >> 3) Create a roadmap for the time between now and the next IETF meeting t= o >> achieve those goals >> >> >> >> I will find a time, is there interest? >> >> _______________________________________________ >> 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 >> > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim > --000000000000211dd005b10340f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm also interested in working on / contributing = to 1=C2=A0+ 2 whenever that kicks off.

=
On Wed, Sep 9, 2020 at 1:12 PM <scim-request@ietf.org> wrote:=

---------- = Forwarded message ----------
From:=C2=A0Darran Rolls <me@darranrolls.com>
To:= =C2=A0"scim@ietf.or= g" <scim@iet= f.org>
Cc:=C2=A0
Bcc:=C2=A0
Date:=C2=A0Wed, 9 Sep 2020 16:0= 7:42 +0000
Subject:=C2=A0[scim] Who's interested in working on what?=

Folks

=C2=A0

Attached is the tally of the responses I=E2=80=99ve = received to date.=C2=A0 Hopefully there are lots of additions to be made, s= o I=E2=80=99m providing the results so far.=C2=A0 If you want to change/add= your interest area, likely best to send that back to be and I=E2=80=99ll continue to manage the document and provide relevant updates = when requited (I=E2=80=99m assuming we don=E2=80=99t have a doc repo until = the WG is reenacted=E2=80=A6)

=C2=A0

=C2=A0




---------- Forwarded message ----------
From:=C2=A0Paul Logs= ton <paul.lo= gston@gmail.com>
To:=C2=A0Darran Rolls <me@darranrolls.com>
Cc:=C2=A0Pa= ul Lanzi <paul@r= emediant.com>, Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.ietf= .org>, "scim= @ietf.org" <= scim@ietf.org>
Bcc:=C2=A0
Date:=C2=A0Wed, 9 Sep 2020 13:11:40 = -0400
Subject:=C2=A0Re: [scim] Moving towards the next IETF Meeting
<= div dir=3D"ltr">
+1 for interest


<= /div>
O= n Wed, Sep 9, 2020 at 12:03 PM Darran Rolls <me@darranrolls.com> wrote:

Me2.=C2=A0

=C2=A0

I=E2=80=99ve not shared the results of our =E2=80=9C= I=E2=80=99m interested to contribute here=E2=80=9D analysis =E2=80=93 I=E2= =80=99ll do that now =E2=80=93 that=E2=80=99s a key input into this process= .=C2=A0 In summary there are gaps but commonality and lots to do=E2=80=A6

=C2=A0

Darran

=C2=A0

From: = scim <scim-bounces@ietf.org>= ; on behalf of Paul Lanzi <paul@remediant.com>
Date: Wednesday, September 9, 2020 at 10:55 AM
To: Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org>= ;
Cc: "scim@ie= tf.org" <sci= m@ietf.org>
Subject: Re: [scim] Moving towards the next IETF Meeting

=C2=A0

Hi Pam - certainly would be interested.

=C2=A0

--Paul

3D"Image=E1=90=A7

=C2=A0

On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle <Pam= ela.Dingle=3D40microsoft.com@dmarc.ietf.org> wrote:

Hi SCIM w= orking group,

= =C2=A0

I would l= ike to propose we get together to do three things:

= =C2=A0

1) Share = each of our goals for where SCIM can go

= =C2=A0

2) Find t= he commonalities

= =C2=A0

3) Create= a roadmap for the time between now and the next IETF meeting to achieve th= ose goals

= =C2=A0

I will fi= nd a time, is there interest?

_______________________________________________
scim mailing list
scim@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/scim

_______________________________________________
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
--000000000000211dd005b10340f7-- --000000000000211dd205b10340f9 Content-Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet; name="SCIM-Next-Topics.xlsx" Content-Disposition: attachment; filename="SCIM-Next-Topics.xlsx" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_kfy6umm30 UEsDBBQABgAIAAAAIQBi7p1oXgEAAJAEAAATAAgCW0NvbnRlbnRfVHlwZXNdLnhtbCCiBAIooAAC AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACs lMtOwzAQRfdI/EPkLUrcskAINe2CxxIqUT7AxJPGqmNbnmlp/56J+xBCoRVqN7ESz9x7MvHNaLJu bbaCiMa7UgyLgcjAVV4bNy/Fx+wlvxcZknJaWe+gFBtAMRlfX41mmwCYcbfDUjRE4UFKrBpoFRY+ gOOd2sdWEd/GuQyqWqg5yNvB4E5W3hE4yqnTEOPRE9RqaSl7XvPjLUkEiyJ73BZ2XqVQIVhTKWJS uXL6l0u+cyi4M9VgYwLeMIaQvQ7dzt8Gu743Hk00GrKpivSqWsaQayu/fFx8er8ojov0UPq6NhVo Xy1bnkCBIYLS2ABQa4u0Fq0ybs99xD8Vo0zL8MIg3fsl4RMcxN8bZLqej5BkThgibSzgpceeRE85 NyqCfqfIybg4wE/tYxx8bqbRB+QERfj/FPYR6brzwEIQycAhJH2H7eDI6Tt77NDlW4Pu8ZbpfzL+ BgAA//8DAFBLAwQUAAYACAAAACEAtVUwI/QAAABMAgAACwAIAl9yZWxzLy5yZWxzIKIEAiigAAIA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKyS TU/DMAyG70j8h8j31d2QEEJLd0FIuyFUfoBJ3A+1jaMkG92/JxwQVBqDA0d/vX78ytvdPI3qyCH2 4jSsixIUOyO2d62Gl/pxdQcqJnKWRnGs4cQRdtX11faZR0p5KHa9jyqruKihS8nfI0bT8USxEM8u VxoJE6UchhY9mYFaxk1Z3mL4rgHVQlPtrYawtzeg6pPPm3/XlqbpDT+IOUzs0pkVyHNiZ9mufMhs IfX5GlVTaDlpsGKecjoieV9kbMDzRJu/E/18LU6cyFIiNBL4Ms9HxyWg9X9atDTxy515xDcJw6vI 8MmCix+o3gEAAP//AwBQSwMEFAAGAAgAAAAhAIE+lJfzAAAAugIAABoACAF4bC9fcmVscy93b3Jr Ym9vay54bWwucmVscyCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAKxSTUvEMBC9 C/6HMHebdhUR2XQvIuxV6w8IybQp2yYhM3703xsqul1Y1ksvA2+Gee/Nx3b3NQ7iAxP1wSuoihIE ehNs7zsFb83zzQMIYu2tHoJHBRMS7Orrq+0LDppzE7k+ksgsnhQ45vgoJRmHo6YiRPS50oY0as4w dTJqc9Adyk1Z3su05ID6hFPsrYK0t7cgmilm5f+5Q9v2Bp+CeR/R8xkJSTwNeQDR6NQhK/jBRfYI 8rz8Zk15zmvBo/oM5RyrSx6qNT18hnQgh8hHH38pknPlopm7Ve/hdEL7yim/2/Isy/TvZuTJx9Xf AAAA//8DAFBLAwQUAAYACAAAACEA0QbCFk0DAADZBwAADwAAAHhsL3dvcmtib29rLnhtbKxVUW+b OhR+n3T/A/I7xQZDAJVOJYBWaZuqruseJxecYhVwrjFNqmr//R47IW3X6arrFiV27GM+f+ec7xyO 32/7zrnjahRyyBA5wsjhQy0bMdxk6Otl5cbIGTUbGtbJgWfono/o/ck/7443Ut1eS3nrAMAwZqjV ep163li3vGfjkVzzASwrqXqmYaluvHGtOGvGlnPdd56PceT1TAxoh5Cq12DI1UrUvJD11PNB70AU 75gG+mMr1uOM1tevgeuZup3Wbi37NUBci07oewuKnL5Oz24Gqdh1B25vSehsFXwj+BEMgz/fBKYX V/WiVnKUK30E0N6O9Av/CfYIeRaC7csYvA6JeorfCZPDAysVvZFVdMCKHsEI/mM0AtKyWkkheG9E Cw/cfHRyvBIdv9pJ12Hr9WfWm0x1yOnYqMtGaN5kaAFLueHPNtS0zifRgZXgBMfIOznI+Vw5DV+x qdOXIOQZHg5GUeKH5iQI47TTXA1M86UcNOhw79efas5iL1sJCncu+L+TUBwKC/QFvsLI6pRdj+dM t86kugx5X0dw3mNTo7jwCrkZOgn15T0RJntZBb8hTVYbfz1weEdq9/9n54GbSmf5nWvlwP+z4iOk 4Au7g4RA2pt9vZ6ZiAffh1ql5PsDjRZlWeDKzcOEukFBEzfOy8INaRUul6T0l7T4Ac6oKK0lm3S7 z7WBzhANf2H6xLazheB0Es0jjQe8/7hm/mmYbT+Mw6arXQm+GR9VYZbO9psYGrnJUBhgcOp+XtII Vhtr+yYa3WbIj+2J3d4HLm5aIEwWlJoSUL4hlqGHEJOEELp0/TwJ3KqipRvHi8hN8lNKqkW5CHBg CXlPGNn2Cczs7AxW8l9MSyXQp81sY4wclZo71FlDbA7nx2rW1SBxM9mDMcF+Yk7wrf44ajuDugTQ IxSfLjBkBpdB6NI48d2YBr4LWfHLcFEWZR6a9Jj2n/6NJmhFns7vFcOyZUpfKlbfwtvogq9yNoKe dg4B36dk8zDOcQAUaUUql5IEu3keUTcsqiBckGJZhtUjWeP+6o0tKPbs05zpCcrTVKZdp2as9ruH zdVuY5+nZ6WXXhQm7vun/+9gdWVT+Mt7PBsHM9rseXP0Tv4DAAD//wMAUEsDBBQABgAIAAAAIQBM 7NBzDwMAAJEHAAAUAAAAeGwvc2hhcmVkU3RyaW5ncy54bWykVU1v2kAQvSPxH0Y+pCfHpI3aKgEi AklDG1oKpDlP7AFvs9519wMCv75jk1Zgk0hVj975evPmzbh98ZRJWJKxQqtOcHLcCoBUrBOhFp3g bnYdfgzAOlQJSq2oE6zJBhfdZqNtrQOOVbYTpM7lZ1Fk45QytMc6J8WWuTYZOv40i8jmhjCxKZHL ZPS21XofZShUALH2ynWC09MAvBK/PPW3D+8+BN22Fd226w6vZtcw7Q9HcP8JQhgqR4a4+Cejfc4P 99o8wkznIrbAOGHqH35S7KDHJd/YduS67ajItM02IBsbkTtut2qaOnS+FjB0lEVl+qr/rVCP1bcJ yTVTB2M0bg13lgyMjV6Kgl5+r5XUcwcDkuSoavpKK7iZwLQktWoc90YvWEp6eAIGixahr5UVyfPX ATKWJJk5BowwK0ideuGqxRKDcxemPKjQxiILs2WY44KDwlaL+S9Hw006HWt5BiMvnQh/oPTELBRu cPXkiGHUGC/0c2ZzjFlXLBAma0lBd5tguZugGGsVVd8bq5ndokTZ62HYOVPLjmoLPS6DtvDLIG6h GvdtpcjUCE+FhBumoGoYoXMwfi5yGMIKU7ktnxs9F5L2eStegJdlTyildGwhdg37murluRRxCb42 zxHyKtxzucNAUFk0YgvFsvLCpFTeDpzpy3ocaeNog9Ark1QLDFUiliLxKGFQyKU2La1iyg+zN9AZ n47DkBdGbDbMWCm8HLOQnlzYOvkju7/KeiaQMUhaUAK9OCZrYYQKF5RRfW5fSMo135AyfbX2AI1B BRMtZY3jMemcB7YSUhba5vnEWjkjHryjaFXcIl674mi8lrTZOJLuHJMkXGtvQoUZhSmftaOFO389 7rsXik8GkqLqATu8Tru9NBtj9BJu9cI6rZqN3WR80quncoeFqu9nBputefsk/y1SrO3LoaqoNqLZ uDSCqb1BZTBFxrC3QM3GZM3WS4OJpPXrgHY9m407pQRMcCkUnys+CJz7X/qpoKi212z0fGJIsLh9 lmmV/EfuFzNF/Evt/gYAAP//AwBQSwMEFAAGAAgAAAAhAMnwxPVhBAAABxEAAA0AAAB4bC9zdHls ZXMueG1sxFhLb9s4EL4vsP+B0F3Rw5JjG5aLOImwBdpugaTAXmmJsolQpEDRqdxi//sOKcmSk/gR N+keEokjzvCb99DTD1XO0CORJRU8srwL10KEJyKlfBlZ3+5je2ShUmGeYiY4iawNKa0Psz//mJZq w8jdihCFQAQvI2ulVDFxnDJZkRyXF6IgHL5kQuZYwVIunbKQBKelZsqZ47vu0Mkx5VYtYZInpwjJ sXxYF3Yi8gIruqCMqo2RZaE8mXxcciHxggHUygtwgipvKH1UyfYQQ312Tk4TKUqRqQuQ64gsowl5 DnfsjB2cdJJA8nmSvNBx/R3dK3mmpMCR5JFq91mzaSa4KlEi1lxF1hCAahNMHrj4zmP9CTzc7JpN yx/oETOg+JYzmyaCCYkUuA4s52kKxzmpd1xjRheSamKGc8o2NdnwGW83+3IKtte7HI2jRjObLoCw hr//7bzh++p3TDf3LY25NaKReshpV5Jihr5xCslM0Oe7F72346jf4yRzZAnBQRnbhupARyUQZlPI aUUkj2GBmvf7TQExyaH81LFl9h3ZvZR44/nh6QylYDTVKJbX/UyAcqioTibbvfCC8Xg8Ci4D9zII /aFvsmTR7Kc8JRVJIesCc2hPD50PBrN5gOoLIVOouG2e+nBsTZpNGckU5Iqky5V+KlHA/4VQCqrS bJpSvBQcM51iLUefEyo1FOXIUisoqm1OP0Wmj2hOOGm/wWKgnLQdILeIT9pfK/eybo2SYLKEMHan lfsn27FblSG+zuNcfQTTg7N04WlfwebNa22jegG228c0AP6XmRAuCrb5ss4XRMamoZnTDFWHarea G9926ytGlzwnOoQAnmH4KoUiiTIN16Sx09eu1rWnpjcEV75eT1RlRxX29ivccteQdfNo2sI+JP4b ytKO3OOIXVw96+rGBn2qNjZaCUl/AGjd4BKwPqn7UpXtN+WrjVGb5i0hhO9jQ3BNlwGg5hPfmvgF sgnONn7b9Vuq13PreZAO5O4vyz7iTRiRFU10OEGBs9B3iYt7UrVJ4RwKrH3R/MwTv8n2gOdAOHQg zqiUW5Weh9NpvjsV2/t5K+hy8EiQNjWxqZB7sug0I758UmvEusO8OkO7kG0qINK3L7jY/a3Hj6ac H4zcXkM8D6EeVHRzg3bW6+E7HXzb+5C+cETWXzDtSUb5Q1unQO/FmjIYw3Q/G5lhvp0GGp4vuiWz XmHrMTzpsIAjrboZwnxV+r5opostMojDlGR4zdT99mNkde+fSUrXORil2fWVPgplRERW9/5Jj3HQ v8EMUCs+lTB3wROtJY2sn7fzy/HNbezbI3c+soMBCe1xOL+xw+B6fnMTj13fvf63d2v9hTuruWRD 5/OCScngZisbZRvwdx0tsnqLGr4ZZwF2H/vYH7pXoefa8cD17GCIR/ZoOAjtOPT8m2Ewvw3jsIc9 PPNu6zqeV9+SNfhwomhOIDRaX7Ue6lPBSbA8oITTesLpfsGY/QcAAP//AwBQSwMEFAAGAAgAAAAh ALMJKK1fAQAAQAUAACMAAAB4bC93b3Jrc2hlZXRzL19yZWxzL3NoZWV0MS54bWwucmVsc8yUwU7D MAyG70i8Q5V7m27AhKZ14wBIO3BB4wGsxG2jJXGVeGPb0xOtSDAJgXoAdksU+be/33Zmi52z2RZD NOQrMSpKkaFXpI1vKvGyesxvRRYZvAZLHiuxxygW88uL2TNa4BQUW9PFLKn4WImWuZtKGVWLDmJB Hfr0UlNwwOkaGtmBWkODclyWExk+a4j5iWa21JUIS30lstW+S5l/1qa6NgrvSW0cev4ihWyTUrDG r5MohAa5l42pZiaysTDI9bHOlp2VOkDN+Su0No/KuLwLVBuLeZlc6uOfSKfSHnaMwYMV8muG8b8z dJgqjOR7DrVJ55B30Bh/bOJgotEfEWlg4JBmBsNHbzSp99a0G889ktv2OI0c1prJeYA0wRwOabL6 MQOX444Hktz8MokDY5mmjgLjAQrwEYK5UyYqKhS5YbZfn4ftPUTveqS06xpt2pRvnJcn/978DQAA //8DAFBLAwQUAAYACAAAACEAwRcQvk4HAADGIAAAEwAAAHhsL3RoZW1lL3RoZW1lMS54bWzsWc2L GzcUvxf6Pwxzd/w1448l3uDPbJPdJGSdlBy1tuxRVjMykrwbEwIlOfVSKKSll0JvPZTSQAMNvfSP CSS06R/RJ83YI63lJJtsSlp2DYtH/r2np/eefnrzdPHSvZh6R5gLwpKWX75Q8j2cjNiYJNOWf2s4 KDR8T0iUjBFlCW75Cyz8S9uffnIRbckIx9gD+URsoZYfSTnbKhbFCIaRuMBmOIHfJozHSMIjnxbH HB2D3pgWK6VSrRgjkvhegmJQe30yISPsDZVKf3upvE/hMZFCDYwo31eqsSWhsePDskKIhehS7h0h 2vJhnjE7HuJ70vcoEhJ+aPkl/ecXty8W0VYmROUGWUNuoP8yuUxgfFjRc/LpwWrSIAiDWnulXwOo XMf16/1av7bSpwFoNIKVprbYOuuVbpBhDVD61aG7V+9Vyxbe0F9ds7kdqo+F16BUf7CGHwy64EUL r0EpPlzDh51mp2fr16AUX1vD10vtXlC39GtQRElyuIYuhbVqd7naFWTC6I4T3gyDQb2SKc9RkA2r 7FJTTFgiN+VajO4yPgCAAlIkSeLJxQxP0AiyuIsoOeDE2yXTCBJvhhImYLhUKQ1KVfivPoH+piOK tjAypJVdYIlYG1L2eGLEyUy2/Cug1TcgL549e/7w6fOHvz1/9Oj5w1+yubUqS24HJVNT7tWPX//9 /RfeX7/+8OrxN+nUJ/HCxL/8+cuXv//xOvWw4twVL7598vLpkxffffXnT48d2tscHZjwIYmx8K7h Y+8mi2GBDvvxAT+dxDBCxJJAEeh2qO7LyAJeWyDqwnWw7cLbHFjGBbw8v2vZuh/xuSSOma9GsQXc Y4x2GHc64Kqay/DwcJ5M3ZPzuYm7idCRa+4uSqwA9+czoFfiUtmNsGXmDYoSiaY4wdJTv7FDjB2r u0OI5dc9MuJMsIn07hCvg4jTJUNyYCVSLrRDYojLwmUghNryzd5tr8Ooa9U9fGQjYVsg6jB+iKnl xstoLlHsUjlEMTUdvotk5DJyf8FHJq4vJER6iinz+mMshEvmOof1GkG/CgzjDvseXcQ2kkty6NK5 ixgzkT122I1QPHPaTJLIxH4mDiFFkXeDSRd8j9k7RD1DHFCyMdy3CbbC/WYiuAXkapqUJ4j6Zc4d sbyMmb0fF3SCsItl2jy22LXNiTM7OvOpldq7GFN0jMYYe7c+c1jQYTPL57nRVyJglR3sSqwryM5V 9ZxgAWWSqmvWKXKXCCtl9/GUbbBnb3GCeBYoiRHfpPkaRN1KXTjlnFR6nY4OTeA1AuUf5IvTKdcF 6DCSu79J640IWWeXehbufF1wK35vs8dgX9497b4EGXxqGSD2t/bNEFFrgjxhhggKDBfdgogV/lxE natabO6Um9ibNg8DFEZWvROT5I3Fz4myJ/x3yh53AXMGBY9b8fuUOpsoZedEgbMJ9x8sa3pontzA cJKsc9Z5VXNe1fj/+6pm014+r2XOa5nzWsb19vVBapm8fIHKJu/y6J5PvLHlMyGU7ssFxbtCd30E vNGMBzCo21G6J7lqAc4i+Jo1mCzclCMt43EmPycy2o/QDFpDZd3AnIpM9VR4MyagY6SHdSsVn9Ct +07zeI+N005nuay6mqkLBZL5eClcjUOXSqboWj3v3q3U637oVHdZlwYo2dMYYUxmG1F1GFFfDkIU XmeEXtmZWNF0WNFQ6pehWkZx5QowbRUVeOX24EW95YdB2kGGZhyU52MVp7SZvIyuCs6ZRnqTM6mZ AVBiLzMgj3RT2bpxeWp1aaq9RaQtI4x0s40w0jCCF+EsO82W+1nGupmH1DJPuWK5G3Iz6o0PEWtF Iie4gSYmU9DEO275tWoItyojNGv5E+gYw9d4Brkj1FsXolO4dhlJnm74d2GWGReyh0SUOlyTTsoG MZGYe5TELV8tf5UNNNEcom0rV4AQPlrjmkArH5txEHQ7yHgywSNpht0YUZ5OH4HhU65w/qrF3x2s JNkcwr0fjY+9AzrnNxGkWFgvKweOiYCLg3LqzTGBm7AVkeX5d+JgymjXvIrSOZSOIzqLUHaimGSe wjWJrszRTysfGE/ZmsGh6y48mKoD9r1P3Tcf1cpzBmnmZ6bFKurUdJPphzvkDavyQ9SyKqVu/U4t cq5rLrkOEtV5Srzh1H2LA8EwLZ/MMk1ZvE7DirOzUdu0MywIDE/UNvhtdUY4PfGuJz/IncxadUAs 60qd+PrK3LzVZgd3gTx6cH84p1LoUEJvlyMo+tIbyJQ2YIvck1mNCN+8OSct/34pbAfdStgtlBph vxBUg1KhEbarhXYYVsv9sFzqdSoP4GCRUVwO0+v6AVxh0EV2aa/H1y7u4+UtzYURi4tMX8wXteH6 4r5c2Xxx7xEgnfu1yqBZbXZqhWa1PSgEvU6j0OzWOoVerVvvDXrdsNEcPPC9Iw0O2tVuUOs3CrVy t1sIaiVlfqNZqAeVSjuotxv9oP0gK2Ng5Sl9ZL4A92q7tv8BAAD//wMAUEsDBBQABgAIAAAAIQCe jxsGFQYAAEQTAAAYAAAAeGwvd29ya3NoZWV0cy9zaGVldDEueG1snFhrb6M4FP2+0v4HxHcH84ao 6SzPTldaabXPz5Q4DSrEWXD6mNH8973GPA0z04zUFALHx9fnnutwufnwWpXKM6mbgp52qr7BqkJO Od0Xp8ed+vdfKfJUpWHZaZ+V9ER26htp1A+3P/9080Lrp+ZICFOA4dTs1CNj562mNfmRVFmzoWdy gjsHWlcZg6/1o9aca5Lt20FVqRkYO1qVFSdVMGzr93DQw6HISUzzS0VOTJDUpMwYxN8ci3PTs1X5 e+iqrH66nFFOqzNQPBRlwd5aUlWp8u3944nW2UMJ637VrSxXXmv4M+Bj9tO01xczVUVe04Ye2AaY NRHzcvm+5mtZPjAt1/8uGt3SavJc8ASOVMaPhaTbA5cxkpk/SOYMZFyuensp9jv1c6R7caLjBLmx YyHdsTwUxGaCdM93I980gjg2vqi3N/sCMsxXpdTksFNDY3uvG6p2e9Ma6J+CvDSTc4VlD3+SkuSM wCS6qnB/PlD6xIH3cAkDZdMCOGWWs+KZRKQsd+qvLlj8v3YSOIUJtGGG6Xk/W9o6+vdaecgaEtHy 32LPjjAlVM6eHLJLyf6gLx9J8XhkcNWBlXPrbPdvMWly8CyEsmnXkdMSOOG/UhW89sBy2auIXVCa G880sKkbtqrkl4bRqp+LRzkMhEy1A+H40scyGdmwN25gczYGEtKOgWM3xrQ2kAvsfGcyqxsIx34y Z/Pt+OBuOxcc+yHexnzPykC8diQcu5Gu/53JIJftEDj2C3O/OZkm0tCmPM5YdntT0xcFahHkbM4Z 39mMra8qPJsG5GgtmzZ4K+djIj6oHQroBq4+3+Ib7RlslMMHiAd20G/KvuqRjjTk2J0K/wdScyAV 0woERDcg9DkiXiKMOSJZ4bDnkHQJseaIu5VpvDnkYw/hFuaa3YsLdlt5U4nAL3ICXEirqIShwL5S X712nGSn+m0qJE0icY8X7iibpEq8gjFk5dZ4HEm6DjNLkRTPXYcBD42JHnlm9oGKkLXx4Jf6XdoM bg05y051WnGkRUXiHug9aiO5Ll5CFtIIiA7bzEjjStJ0mKm/ddlXAgMrHJUZzTlThm/mUtm6oOh1 ruEkvWvkWhP3Zq6R6iRegSyUWcHovqRMh5mZRiqnuw4zM81X9hz+KCdLM2zd7y0oTtJ7RspSJO5N PSOVQbxELIQREB0CG3JtSJWSdpipZYxx0e22cicwM8uMHp9ZBnZ3WRf/astwkt4ykh8icW9mGakI 4hWIITkvWcNIKUgHTL+93nVXZgYZR82E4BHKSuj61XtuS9N7RHJA1N2cmkSydLwCWbhkDSPvuR1m biUpN3cdaOaTUfi5PFCIC3nM6+XhNL1VJB9Eurg584q0LcRrmIVZVkHy1juCBrv0l6Z+McYI5oKs PCPpBpjout0WHuvHPUUyQ9TdnP0QSaUer2CWeohJpjzGQo4eM6ohrszcMW5GQgzRLohnx+PbmdRl cXqCJ/vhXDQwKexo9Za3QPX9HrK8L5pzmb2J3qqBznkPT5+szvInUm8Kwg5tz7ynubavswNDx8uJ oSYvKlQ9o3P2CB26NmmrHCPBQepEKDVMGzme5aIgtAMUeX4SJrqRWCb+wp+x5LDgp3UIC1a7CItR 6FPGgI4MencR0ZkweHFATyKq/ALntYisbccRBicMbZ8XxGnoQEAuDj2ELStCPk4sFNumj3EaJKEZ r8YHGRvig+eIK+J7yY6liO1c00NRknlEum1gW08jhD3XRoll6ShMQ4zs1I3jOLTSIE5WIwI3DBHB T9C1iYSeIqsLERh/R4D20JYyMk1mGJuej/0QGZaPUZpaCfL8OERJ6ODAtDzbCKK10JJpaOC3ITR4 z1Iyuq1ozcinbCNC+CUvmpzyVxSTPNm6kwa6g5Hj2i6yTStAQWDHyLZDrBuWZ+F03Ud8yxpkAVNd K8tjXXz6BDlqLX7OKkRe2VQTy0t9L0h8FPuOjwzbClGAjQQ5ZpImfpCkHvZbTbRpEUKhkN+yGqql UUpyaLtv7ijRnuMN3w/omffkLuj1QBl02f23I7ytItCh4A347kApuF184e8Ihvdft/8DAAD//wMA UEsDBBQABgAIAAAAIQDCXlkIkAEAABsDAAAQAAgBZG9jUHJvcHMvYXBwLnhtbCCiBAEooAABAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJySTW/bMAyG7wP6HwzdGzltUQyBrGJIV/SwYgGSdmdO pmOhsiSIrJHs10+20dTZdtqNHy9ePqKo7g6dK3pMZIOvxHJRigK9CbX1+0o87x4uP4uCGHwNLnis xBFJ3OmLT2qTQsTEFqnIFp4q0TLHlZRkWuyAFrntc6cJqQPOadrL0DTW4H0wbx16lldleSvxwOhr rC/jyVBMjque/9e0Dmbgo5fdMWZgrb7E6KwBzq/UT9akQKHh4gmM9RyoLb4eDDol5zKVObdo3pLl oy6VnKdqa8DhOo/QDThCJT8K6hFhWN8GbCKtel71aDikguyvvMArUfwEwgGsEj0kC54z4CCbkjF2 kTjpHyG9UovIpGQWTMUxnGvnsb3Ry1GQg3PhYDCB5MY54s6yQ/rebCDxP4iXc+KRYeKdcLYD3zRz zjc+OU/6w3sdugj+mBun6Jv1r/Qcd+EeGN/XeV5U2xYS1vkHTus+FdRj3mRyg8m6Bb/H+l3zd2M4 g5fp1vXydlFel/lfZzUlP65a/wYAAP//AwBQSwMEFAAGAAgAAAAhAPLBMsZdAQAAdwIAABEACAFk b2NQcm9wcy9jb3JlLnhtbCCiBAEooAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAISSX0+D MBTF3038DqTvUGA6JwFm1OzJRRO3aHxr2gtrpH/SVpFvb2EbsmjiY3vO/fWcm+bLL9EEn2AsV7JA SRSjACRVjMu6QNvNKlygwDoiGWmUhAJ1YNGyPD/Lqc6oMvBklAbjONjAk6TNqC7QzjmdYWzpDgSx kXdIL1bKCOL80dRYE/pOasBpHM+xAEcYcQT3wFCPRHRAMjoi9YdpBgCjGBoQIJ3FSZTgH68DI+yf A4MycQruOu07HeJO2YzuxdH9ZflobNs2amdDDJ8/wa/rh+ehashlvysKqMwZzagB4pQp15waZVXl gseq4hSCrQWT44mj32ZDrFv7xVcc2G1XMkm1cd1NLQhvIqpEjn+b/CtDqf1TwAIfM9uXOiovs7v7 zQqVaZzGYXwVpukmWWQXl9ns+q3PcDLfx95fiEOS/4iJh843ydzjsjSeEI+Acsh9+lXKbwAAAP// AwBQSwECLQAUAAYACAAAACEAYu6daF4BAACQBAAAEwAAAAAAAAAAAAAAAAAAAAAAW0NvbnRlbnRf VHlwZXNdLnhtbFBLAQItABQABgAIAAAAIQC1VTAj9AAAAEwCAAALAAAAAAAAAAAAAAAAAJcDAABf cmVscy8ucmVsc1BLAQItABQABgAIAAAAIQCBPpSX8wAAALoCAAAaAAAAAAAAAAAAAAAAALwGAAB4 bC9fcmVscy93b3JrYm9vay54bWwucmVsc1BLAQItABQABgAIAAAAIQDRBsIWTQMAANkHAAAPAAAA AAAAAAAAAAAAAO8IAAB4bC93b3JrYm9vay54bWxQSwECLQAUAAYACAAAACEATOzQcw8DAACRBwAA FAAAAAAAAAAAAAAAAABpDAAAeGwvc2hhcmVkU3RyaW5ncy54bWxQSwECLQAUAAYACAAAACEAyfDE 9WEEAAAHEQAADQAAAAAAAAAAAAAAAACqDwAAeGwvc3R5bGVzLnhtbFBLAQItABQABgAIAAAAIQCz CSitXwEAAEAFAAAjAAAAAAAAAAAAAAAAADYUAAB4bC93b3Jrc2hlZXRzL19yZWxzL3NoZWV0MS54 bWwucmVsc1BLAQItABQABgAIAAAAIQDBFxC+TgcAAMYgAAATAAAAAAAAAAAAAAAAANYVAAB4bC90 aGVtZS90aGVtZTEueG1sUEsBAi0AFAAGAAgAAAAhAJ6PGwYVBgAARBMAABgAAAAAAAAAAAAAAAAA VR0AAHhsL3dvcmtzaGVldHMvc2hlZXQxLnhtbFBLAQItABQABgAIAAAAIQDCXlkIkAEAABsDAAAQ AAAAAAAAAAAAAAAAAKAjAABkb2NQcm9wcy9hcHAueG1sUEsBAi0AFAAGAAgAAAAhAPLBMsZdAQAA dwIAABEAAAAAAAAAAAAAAAAAZiYAAGRvY1Byb3BzL2NvcmUueG1sUEsFBgAAAAALAAsA0QIAAPoo AAAAAA== --000000000000211dd205b10340f9-- From nobody Tue Oct 6 09:51:44 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 782003A0CEC for ; Tue, 6 Oct 2020 09:51:43 -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, HTML_FONT_LOW_CONTRAST=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 (1024-bit key) header.d=slack-corp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QkaOzPWb1iA for ; Tue, 6 Oct 2020 09:51:41 -0700 (PDT) Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 3D0FD3A0CE3 for ; Tue, 6 Oct 2020 09:51:41 -0700 (PDT) Received: by mail-il1-x12a.google.com with SMTP id l16so11578264ilt.13 for ; Tue, 06 Oct 2020 09:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=slack-corp.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7UBPLP0sDUuKGd1eAX8eAIcgPqUmbTsBk4klZcbSPak=; b=jSSLE6UTwajKoEc7NeCOLlARbHV3NJZlCR+t48brXKICTM2cKbx2aQcFGX7C57nhjm TmJUTawUZ8Byzu2jJK9IrxoWiitSJH++1WSXXYL5XBLC8H08Ah8DeLHVfTwKUdHOas4s Y1jj7iIggJk14tBNuVPmIRT6zM7/jbb/ubWiQ= 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; bh=7UBPLP0sDUuKGd1eAX8eAIcgPqUmbTsBk4klZcbSPak=; b=DvWv9FF+SAfetKc7vfrXFuf0KdGFoRGCXe9EA/ZiLExz+KWJgx6gNrFjtztdWWOqdl SMZXUy+UbwHfQBBwE3/M/VpDeb7BOvU2I1k4hV6HOc7Hcf6ZjGkzjAxvff88D2bGLaLv u4ibsF80Vd42Epmvvx/apanR8v9wcmUETBFEmEsgARZPiYGA0DBGwtE/tdMJjS3x1QQz VCq12mK+3kvinSUkFMBEI+k0Pl5/9ZnszLtGVi3mj6iGp10XROdU8dmE15pwy6+TxJpx IszRvt36lfVHLpjdoZAaENdNtykX+8ZTu57qeCtHlxcgEt+Dza7ejAJd9eHfQEW9aKNq Rcyg== X-Gm-Message-State: AOAM53399nf/A84tevUN2uvARkg4UzdTzF5oD5qeOMFLnLWUowHsNRGZ /b/J2Vk2i2m+9N+Hk/EbeGU3YwRUOs+AxU/1BHWjMZoBWJg= X-Google-Smtp-Source: ABdhPJxP/T9ecpsP6QxDos96+HOssqfmjpathxVtK0czQFEsRK564Q3vpxz+hRzEBpyCJjOGy5pxeGLpW57G8gUiS6Y= X-Received: by 2002:a92:1589:: with SMTP id 9mr4431843ilv.292.1602003100028; Tue, 06 Oct 2020 09:51:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Audrei Drummond Date: Tue, 6 Oct 2020 12:51:29 -0400 Message-ID: To: scim@ietf.org Content-Type: multipart/alternative; boundary="000000000000b5013805b10369cc" Archived-At: Subject: Re: [scim] Moving towards the next IETF Meeting X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2020 16:51:43 -0000 --000000000000b5013805b10369cc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +1, I'm also interested On Wed, Sep 9, 2020 at 12:03 PM wrote: > Send scim mailing list submissions to > scim@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/scim > or, via email, send a message with subject or body 'help' to > scim-request@ietf.org > > You can reach the person managing the list at > scim-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of scim digest..." > Today's Topics: > > 1. Moving towards the next IETF Meeting (Pamela Dingle) > 2. PRECIS questions (Sarah Mundy) > 3. Re: Moving towards the next IETF Meeting (Paul Lanzi) > 4. Re: Moving towards the next IETF Meeting (Darran Rolls) > > > > ---------- Forwarded message ---------- > From: Pamela Dingle > To: "scim@ietf.org" > Cc: > Bcc: > Date: Wed, 9 Sep 2020 15:34:59 +0000 > Subject: [scim] Moving towards the next IETF Meeting > Hi SCIM working group, > > I would like to propose we get together to do three things: > > 1) Share each of our goals for where SCIM can go > > 2) Find the commonalities > > 3) Create a roadmap for the time between now and the next IETF meeting to > achieve those goals > > I will find a time, is there interest? > > > > ---------- Forwarded message ---------- > From: Sarah Mundy > To: scim@ietf.org > Cc: > Bcc: > Date: Mon, 31 Aug 2020 08:22:03 -0700 > Subject: [scim] PRECIS questions > Hi all, > > A couple of questions about PRECIS string comparison for SCIM 2.0: > > 1. The SCIM 2.0 spec references RFCs 7564 and 7613, which are obsolete > drafts of PRECIS. Are folks instead using the final versions, RFCs 8264 a= nd > 8265? > > 2. Can anyone point me to a stable, open-source library of PRECIS tools, > preferably in Java? What are other server implementers using? I haven't > been able to find anything but maybe I am not using the right keywords in > my searches. > > Thanks, > Sarah > > > > ---------- Forwarded message ---------- > From: Paul Lanzi > To: Pamela Dingle > Cc: "scim@ietf.org" > Bcc: > Date: Wed, 9 Sep 2020 08:39:28 -0700 > Subject: Re: [scim] Moving towards the next IETF Meeting > Hi Pam - certainly would be interested. > > --Paul > =E1=90=A7 > > On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle 40microsoft.com@dmarc.ietf.org> wrote: > >> Hi SCIM working group, >> >> I would like to propose we get together to do three things: >> >> 1) Share each of our goals for where SCIM can go >> >> 2) Find the commonalities >> >> 3) Create a roadmap for the time between now and the next IETF meeting t= o >> achieve those goals >> >> I will find a time, is there interest? >> _______________________________________________ >> scim mailing list >> scim@ietf.org >> https://www.ietf.org/mailman/listinfo/scim >> > > > > ---------- Forwarded message ---------- > From: Darran Rolls > To: Paul Lanzi , Pamela Dingle 40microsoft.com@dmarc.ietf.org> > Cc: "scim@ietf.org" > Bcc: > Date: Wed, 9 Sep 2020 16:03:16 +0000 > Subject: Re: [scim] Moving towards the next IETF Meeting > > Me2. > > > > I=E2=80=99ve not shared the results of our =E2=80=9CI=E2=80=99m intereste= d to contribute here=E2=80=9D > analysis =E2=80=93 I=E2=80=99ll do that now =E2=80=93 that=E2=80=99s a ke= y input into this process. In > summary there are gaps but commonality and lots to do=E2=80=A6 > > > > Darran > > > > *From: *scim on behalf of Paul Lanzi < > paul@remediant.com> > *Date: *Wednesday, September 9, 2020 at 10:55 AM > *To: *Pamela Dingle > *Cc: *"scim@ietf.org" > *Subject: *Re: [scim] Moving towards the next IETF Meeting > > > > Hi Pam - certainly would be interested. > > > > --Paul > > [image: Image removed by sender.]=E1=90=A7 > > > > On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle 40microsoft.com@dmarc.ietf.org> wrote: > > Hi SCIM working group, > > > > I would like to propose we get together to do three things: > > > > 1) Share each of our goals for where SCIM can go > > > > 2) Find the commonalities > > > > 3) Create a roadmap for the time between now and the next IETF meeting to > achieve those goals > > > > I will find a time, is there interest? > > _______________________________________________ > 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 > --000000000000b5013805b10369cc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
+1, I'm also interested

On Wed, Sep 9, 2020 = at 12:03 PM <scim-request@ietf.= org> wrote:
Send scim mailing list submissions to
=C2=A0 =C2=A0 =C2=A0 =C2=A0 scim@ietf.org

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

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

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

=C2=A0 =C2=A01. Moving towards the next IETF Meeting (Pamela Dingle)
=C2=A0 =C2=A02. PRECIS questions (Sarah Mundy)
=C2=A0 =C2=A03. Re: Moving towards the next IETF Meeting (Paul Lanzi)
=C2=A0 =C2=A04. Re: Moving towards the next IETF Meeting (Darran Rolls)



---------- Forwarded message ----------
From:=C2=A0Pamela Di= ngle <P= amela.Dingle@microsoft.com>
To:=C2=A0"scim@ietf.org" <scim@ietf.org>
Cc:=C2=A0
Bcc:= =C2=A0
Date:=C2=A0Wed, 9 Sep 2020 15:34:59 +0000
Subject:=C2=A0[scim]= Moving towards the next IETF Meeting
Hi SCIM working group,

I would like to propose we get together to do three things:

1) Share each of our goals for where SCIM can go

2) Find the commonalities

3) Create a roadmap for the time between now and the next IETF meeting to a= chieve those goals

I will find a time, is there interest?



---------- Forwarded message ----------
From:=C2=A0Sarah Mun= dy <the.s= arah.mundy@gmail.com>
To:=C2=A0scim@ietf.org
Cc:=C2=A0
Bcc:=C2=A0
Date:=C2= =A0Mon, 31 Aug 2020 08:22:03 -0700
Subject:=C2=A0[scim] PRECIS questions=
Hi all,

A couple of ques= tions about PRECIS string comparison for SCIM 2.0:

1. The SCIM 2.0 spec references RFCs 7564 and 7613, which are obsolete dra= fts of PRECIS. Are folks instead using the final versions, RFCs 8264 and 82= 65?

2. Can anyone point me to a stable, open-sourc= e library of PRECIS tools, preferably in Java? What are other server implem= enters using? I haven't been able to find anything but maybe I am not u= sing the right keywords in my searches.

Thanks= ,
Sarah



---------- Forwarded message ----------
From:=C2=A0Paul Lanz= i <paul@remedian= t.com>
To:=C2=A0Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.= ietf.org>
Cc:=C2=A0"scim@ietf.org" <scim@ietf.org>
Bcc:=C2=A0
Date:=C2=A0Wed, 9 Se= p 2020 08:39:28 -0700
Subject:=C2=A0Re: [scim] Moving towards the next I= ETF Meeting
Hi Pam - certainly would be interested.
--Paul
3D""=E1=90=A7




---------- Forwarded message ----------
From:=C2=A0Darran Ro= lls <me@darranro= lls.com>
To:=C2=A0Paul Lanzi <paul@remediant.com>, Pamela Dingle <Pamel= a.Dingle=3D40microsoft.com@dmarc.ietf.org>
Cc:=C2=A0"scim@ietf.org" <scim@ietf.org>
Bcc:=C2= =A0
Date:=C2=A0Wed, 9 Sep 2020 16:03:16 +0000
Subject:=C2=A0Re: [scim= ] Moving towards the next IETF Meeting

Me2.=C2=A0

=C2=A0

I=E2=80=99ve not shared the results of our =E2=80=9C= I=E2=80=99m interested to contribute here=E2=80=9D analysis =E2=80=93 I=E2= =80=99ll do that now =E2=80=93 that=E2=80=99s a key input into this process= .=C2=A0 In summary there are gaps but commonality and lots to do=E2=80=A6

=C2=A0

Darran

=C2=A0

From: = scim <scim-bounces@ietf.org>= ; on behalf of Paul Lanzi <paul@remediant.com>
Date: Wednesday, September 9, 2020 at 10:55 AM
To: Pamela Dingle <Pamela.Dingle=3D40microsoft.com@dmarc.ietf.org>= ;
Cc: "scim@ie= tf.org" <sci= m@ietf.org>
Subject: Re: [scim] Moving towards the next IETF Meeting

=C2=A0

Hi Pam - certainly would be interested.

=C2=A0

--Paul

3D"Image=E1=90=A7

=C2=A0

On Wed, Sep 9, 2020 at 8:37 AM Pamela Dingle <Pam= ela.Dingle=3D40microsoft.com@dmarc.ietf.org> wrote:

Hi SCIM w= orking group,

= =C2=A0

I would l= ike to propose we get together to do three things:

= =C2=A0

1) Share = each of our goals for where SCIM can go

= =C2=A0

2) Find t= he commonalities

= =C2=A0

3) Create= a roadmap for the time between now and the next IETF meeting to achieve th= ose goals

= =C2=A0

I will fi= nd a time, is there interest?

_______________________________________________
scim mailing list
scim@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/scim

_______________________________________________
scim mailing list
scim@ietf.org
https://www.ietf.org/mailman/listinfo/scim
--000000000000b5013805b10369cc-- From nobody Mon Oct 19 03:56:52 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 745AA3A0AE6 for ; Mon, 19 Oct 2020 03:56:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=sap.com header.b=P8yHRF4P; dkim=pass (1024-bit key) header.d=sap.onmicrosoft.com header.b=DdI+cOtO 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 KpoJL1cNkljZ for ; Mon, 19 Oct 2020 03:56:49 -0700 (PDT) Received: from esa3.sap.c3s2.iphmx.com (esa3.sap.c3s2.iphmx.com [68.232.159.191]) (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 244583A0ADF for ; Mon, 19 Oct 2020 03:56:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sap.com; i=@sap.com; q=dns/txt; s=it-20200722; t=1603105010; x=1634641010; h=from:to:subject:date:message-id:mime-version; bh=Yk0tP8VH7FYqGNlXoqXRdC5NntmtVTt4pLYPa5VR/jk=; b=P8yHRF4P/fDQG1bJ9p/kBBiMdtnIsmXCV0rq3y6kvSJhBTac/HmIZI5U ZXEAsNrpD3I4vG8a0Svn6x0aDMT/HNw79+LVJngJWyqhaL5GRqnf4hkwB RHrdES3vM6tqxpegTaN7fpOh8KSjsLNYbH1NMAKw/z7LNuAxiVJtO/MNt L53qseHujPW2NxHm5zRCoXgVG/kWyYtvTuluKKu0bvK53syuyUXH0CfJv p3jL0I51lg+Rx1HJQrQT00g8rJ/aNd4lMrDwFb/zXrUzk1RaQHExlhaae vVsGkyGId7tD0RVHR9KirVrOYDUBz3GFdw2JnthSGdcA4pNgsS8kcWbBm Q==; IronPort-SDR: gjTGb6a/agvG8i7iygEW/DRBt83Kimg6scF5h2u+gzIwPWmGp3YoTpDyHFpIvDGSjZgrytuVsN w6/oMO2U8W0DWRSHjg8MxdPpxpXmmCHpLwKJtrl+krVNTXD7jplp9hUq65qAb5FlbEnyHIcAvB hRYgvfnGtNaF++l8VzBQ7eq9L2i+Flm+vIsPkiAitlQaUzmaiQCButAZti1bfLo6sfVbqwVDTP bQ4KNSDnv3Fqm+eeF4w494iO94hMuDZaIuUAR/l3KidqUnK6mnjmY/y1nG6UeOraAYBGxLIU6M LvdilKi0aGsgs1Q/x+be7DIE X-Amp-Result: SKIPPED(no attachment in message) Received: from smtpgw01.mail.net.sap (HELO smtpgw.sap-ag.de) ([155.56.66.96]) by esa3.sap.c3s2.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 19 Oct 2020 12:56:46 +0200 Received: from EUR02-VE1-obe.outbound.protection.outlook.com (104.47.6.58) by smtpgw01.mail.net.sap (155.56.66.96) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 19 Oct 2020 12:56:45 +0200 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C0Nvo8uF4l7MCJqDym4lpMp/+QerB1NbxOa4XZxECQtX5Qf+UeTSRULzyRPb/NsqVNoA7NEGWv79tfPq4yAJchAsUhzNKftvpTvgIJY5U6+v+RdPI0zYUgJitEoNaqU8lSSXOFcauD+mNRwM04g1Fd44q9JIbywMCYzeqNMSqTWpDWwLhakFlb8Uu6BFrg4r7UQKdJfGIOrkcDJTG14XqBKPB7FvHVOHLpIV+m6Th6VoNR4XTmvPxPts8fQVI6ai1bQg0/6HNUV2IEyYYZzbMj20amXI+4wPnMCEd9NCpoZcy+Z82EdMXmRMZmSl7HmGZ2mj/3OHrVdY3H8MVYCw5w== 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=Yk0tP8VH7FYqGNlXoqXRdC5NntmtVTt4pLYPa5VR/jk=; b=Wd6HSsHDifGGTmjulFzjFuj+n/q5AYfN7qw3qk7LJrd5vD/ajyNeGuD9FOyN9bXdOvOvZVREiF+YJmSoD4j0Lbr9CV7Y9tzzCIlgC5hMyxKSkIe946tGAIQPC3iEmreoRmc02Th9SFHgdovkNTClfzy6t+NNFb4tEY+Tb6fdl7QkiQcoWUubKyr6VnU+LRrpRfa2rq+k2OfprxS53FyQjGhigGWk7DWrCxIZPeGsz2ZteNoM8KHbkKvjD0sgBY9wtYRXczGyzxFimnqVP+Rji0P99Bpee8bOt66XyOBmLBNgW5DnpYJO2lvqCfEqkCl6JXY/0ZBHFP27pW3eZ53E7g== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sap.com; dmarc=pass action=none header.from=sap.com; dkim=pass header.d=sap.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sap.onmicrosoft.com; s=selector2-sap-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Yk0tP8VH7FYqGNlXoqXRdC5NntmtVTt4pLYPa5VR/jk=; b=DdI+cOtOfv25BtsGlCFy0FQlTAFkgqRRpx3xFn9hWJWC8ux9nLNdqnrUIknOWzK27/yti0WPObLLr22vqidHgT2mdKS2CTGVZKevhyvpu59gvxEhIj4wk2RNR0+2H1EFeOaCfQGdG+fnWNfOrUcaZg5Gas9NHSIIHAj4N6c9sUg= Received: from VI1PR02MB5200.eurprd02.prod.outlook.com (2603:10a6:803:b7::14) by VI1PR02MB3213.eurprd02.prod.outlook.com (2603:10a6:802:1a::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.21; Mon, 19 Oct 2020 10:56:41 +0000 Received: from VI1PR02MB5200.eurprd02.prod.outlook.com ([fe80::29cf:9c9d:14c2:7584]) by VI1PR02MB5200.eurprd02.prod.outlook.com ([fe80::29cf:9c9d:14c2:7584%3]) with mapi id 15.20.3477.028; Mon, 19 Oct 2020 10:56:41 +0000 From: "Karaimin, Aleyidin" To: "scim@ietf.org" Thread-Topic: Extend core schema multivalue complex attribute Thread-Index: AQHWpgQfQMGrLicbAUeZv9T/Z311KA== Date: Mon, 19 Oct 2020 10:56:41 +0000 Message-ID: Accept-Language: en-US, bg-BG Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [78.90.93.41] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: e6062bee-6ea8-44c2-fb54-08d8741da902 x-ms-traffictypediagnostic: VI1PR02MB3213: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: vMUDkPXNO3S9MnQ/gerlvxb8Cnl2GgZbAHliIrPwrnHnjQHaKb+DoYXydut/rFOqnZzYcJOLswTvzH+YGYcyc4U2bAFlCvJgV583kyw1uM8WxTBsozNSRSg804OqxROAG0e7jLIuyrtWvKJEK7GqzKJv6VkRHdDYc6l9QAszsS1QoNSYeyGtVx2C7nGDEIJFqY7BZtQu4tcMuxTPUF4Jqm/tSrj7J7ds7pBg5YgtyLiuCnF1t8SYvvOfeea1qeYJcBcrI1mPp+dx+vAdgfOIJurE8yLNxdntBW5j2WJwoex1Arb0YtEG9vcOoVRqZMW4OINNZ1fVpqYeA5PUFTJC7g== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR02MB5200.eurprd02.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(396003)(376002)(346002)(39860400002)(366004)(136003)(316002)(6506007)(8676002)(7696005)(86362001)(26005)(8936002)(186003)(66946007)(33656002)(71200400001)(66446008)(66476007)(64756008)(52536014)(9686003)(478600001)(6916009)(2906002)(5660300002)(76116006)(66556008)(55016002); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata: uvYFAIjiGKUiEFFC9xAMiuIsEPvJbf+FzSszjgRgYuzphyZ50mCx2zb+witJ24ISEnjJfLGIVn+RrtsOMJebEVtNgZ5Y3HKlS2a7gBud2cJN17ZaS+QLEZSbvNhkIg3YrSfRHdFgc8gYQEz1OMKngxna/AsWsY+0eve/THDqGeBH8orG9zgVoF3lujZJL2SyJjB8YwHSFDUKBqTNeiFrHewVUC68S0enJ1q/RVdwXk84wXjqRhStpw2VEwdGbVZ3FT7Y3QysVXrDVqIQG5+L8FcpfhxK3KTV1do8td/7SjgPPvD2grgHMkuzxzm1qJk5Hbh86HD9l72IUCau4Zwvxj7jRic2Y3hcKr22GmuJ+wS1Icz87qT37/CPVyzwhPJ+vVRBzzIb+nizbgFwmdG5lN96eYNBM9Abe20e4MtOe+BBjRahUCOYeSbmF4UR4DNjub2ebawPV8XE4CzCVxU62P2qhFDKbAIdZvH1bYYGGUsG/y4JAOULKX/6VL/bjX9O8bRe4VNyO4wpe1+hGjd4fEexP+qUoIbR/5bqj/cevFWRbbs+MjUbFmsZxcY2Ryh8YG45wf/bMGp3936kMccoK40PYaN9AhU55O1IsNmssXWBdTEhUN/PF1V/MQ1fgYXGJx294RDpvEVEM16O5JViDA== x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_VI1PR02MB5200B81A304D8131E2E9DA97F81E0VI1PR02MB5200eurp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: VI1PR02MB5200.eurprd02.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: e6062bee-6ea8-44c2-fb54-08d8741da902 X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Oct 2020 10:56:41.0264 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 42f7676c-f455-423c-82f6-dc2d99791af7 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: zlzpArOQbpaHljHxWIC4LPppJc/M2Abtp/Pq1vpuzZGmmPc0/GQcjvjYNhBdRBwya5A64oErHZDkUQSLj0YbhSsw2+a/1G5GLGGwTaW9aD4= X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR02MB3213 Archived-At: Subject: [scim] Extend core schema multivalue complex attribute X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2020 10:56:51 -0000 --_000_VI1PR02MB5200B81A304D8131E2E9DA97F81E0VI1PR02MB5200eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi I would like to ask you for possible way to extend multivalue attribute. Ou= r use cases require to support additional sub-attributes for some User and = Groups multivalue complex attributes. For example: { "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "userName": "sample", "emails": [ { "type": "work", "value" "sample@example.com", "otherAttribute": "value" // the name is kn= own (It is defined by us) } ] } According to spec, this will conflict with the core schema. I know that I c= ould define extension schema and add this attribute but this would lead to = a lot duplicate data. { "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "userName": "sample", "emails": [ { "type": "work", "value" "sample@example.com", ... } ], "urn:ietf:params:scim:schemas:extension:enterprise:2.0:Emails" : { "emails": [ { "type": "work", "value" "sample@example.com", "otherAttribute": "value" // the name is kn= own (It is defined by us) ... } ] } } My question is if there is another solution to achieve this. Thank you. Best Regards Aleydin --_000_VI1PR02MB5200B81A304D8131E2E9DA97F81E0VI1PR02MB5200eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi

 

I would like to ask you for possible way to extend m= ultivalue attribute. Our use cases require to support additional sub-attributes for some User and Groups multivalue complex attributes.= For example:

 

{

        &nbs= p;       "schemas": [

        "urn= :ietf:params:scim:schemas:core:2.0:User"

    ],

    "userName": "sampl= e",

    "emails": [<= /p>

         &nb= sp;      {

         &nb= sp;            =           "type": &q= uot;work",

         &nb= sp;            =           "value" &q= uot;sample@example.com",

         &nb= sp;            =           "otherAttribute= ": "value" // the name is known (It is defined by us)

         &nb= sp;      }

    ]

}

 

According to spec, this will conflict with the core = schema. I know that I could define extension schema and add this attribute = but this would lead to a lot duplicate data.

 

{

        &nbs= p;       "schemas": [

        "urn= :ietf:params:scim:schemas:core:2.0:User"

    ],

    "userName": "sampl= e",

    "emails": [<= /p>

         &nb= sp;      {

         &nb= sp;            =           "type": &q= uot;work",

         &nb= sp;            =           "value" &q= uot;sample@example.com",

         &nb= sp;            =           ...

         &nb= sp;      }

    ],

    "urn:ietf:params:scim:schema= s:extension:enterprise:2.0:Emails" : {

         &nb= sp;      "emails": [

         &nb= sp;      {

         &nb= sp;            =           "type": &q= uot;work",

         &nb= sp;            =           "value" &q= uot;sample@example.com",

         &nb= sp;            =           "otherAttribute= ": "value" // the name is known (It is defined by us)

         &nb= sp;            =           ...

         &nb= sp;      }

    ]

    }

}

 

My question is if there is another solution to achieve this.

Thank you.

 

Best Regards

Aleydin

--_000_VI1PR02MB5200B81A304D8131E2E9DA97F81E0VI1PR02MB5200eurp_-- From nobody Tue Oct 20 12:54:14 2020 Return-Path: X-Original-To: scim@ietfa.amsl.com Delivered-To: scim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E4C3A105D for ; Tue, 20 Oct 2020 12:54:13 -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=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 FhvwfHZyBamx for ; Tue, 20 Oct 2020 12:54:09 -0700 (PDT) Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 C062D3A07CE for ; Tue, 20 Oct 2020 12:54:09 -0700 (PDT) Received: by mail-pl1-x636.google.com with SMTP id t22so1578630plr.9 for ; Tue, 20 Oct 2020 12:54:09 -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=wW3Ge622mZsdpfEKveJoGUntoEBXyFJYOqabcyDsLqA=; b=Ygxntxs1gUjGVUt8MIg2PHlUcn4TUFOKuSy7liOTuEDAg2isdkkTHovyGAG/vrJOPN Eem6t6KTgH67Xvwbfvf73mM8/QFsLYUF0Xm16IIhKmQWddFgO+Y1KyK+hVGybCuZjYan JivkL6RqMMh/qjjMq6BBkIovrnQSnIgHCL0a/Df/9aipOTYoE2qlBDfbIVy3PGsFbPyg x212Ng5dZDw/eC2e7zp0gerKwA30XXioA5YQKtuai/jGpgb0RFJc711pIuJC8u15ijx+ Zqoel7T7DGd4siA6aaDjtgWot8fns59BG4Ufey1ELFaXSVT9Cf/3yO/Jrb9Klw808qD7 6Oyg== 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=wW3Ge622mZsdpfEKveJoGUntoEBXyFJYOqabcyDsLqA=; b=HGSI6D1wThrD3wuMRNsF0zwMnqSNof9FNWSondz0M09zh05gokBVWf8ED6Vx7IgZyx yAKzlb38QlivyS5r+c8zIPeNcYydJLK3UKRTXugtYP3Cqt2OSi3Pxiti69NhvqQJL1NO hXZQD3sxku1bAjuAY7VYMp5XP4hyBjwd7v8gITFGp4FbAyiLQ2VQnMZfQH/PRzp7SnpQ x8QQsdEerow+/I2VBKVCJ7xH7TZcEA+ou6PgroX/r5xrsoTgLDE76U8deGN+MhePQ/uz YZWW0bjjkaS+OI9Joj7yOpVMzMepUiZQFtjmqjB3nKyyxU2YYwdXVhDvWLK5Z0RMqPue htIg== X-Gm-Message-State: AOAM530+10dSt2whFuxp+DB5IIpqBNNnhHHzCPt2821v540wcq7cJxif 7K7sydlb9Q1xLlt32kSsnNgq3A== X-Google-Smtp-Source: ABdhPJy4TJ6z0Q7o11ktIjiPPd0oKbfxe9gpP9VcSJw/Vdie1gEQxmLfBOs1xOC9lLrusrFguLpYJA== X-Received: by 2002:a17:90b:2345:: with SMTP id ms5mr3210052pjb.141.1603223649026; Tue, 20 Oct 2020 12:54:09 -0700 (PDT) Received: from ?IPv6:2001:569:7a71:1d00:6913:8e7:e2a2:d95a? (node-1w7jr9qrfoxx94eujgqq75umy.ipv6.telus.net. [2001:569:7a71:1d00:6913:8e7:e2a2:d95a]) by smtp.gmail.com with ESMTPSA id jx17sm23795pjb.10.2020.10.20.12.54.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Oct 2020 12:54:08 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-5D442460-2021-4B87-A7A7-696354327F37 Content-Transfer-Encoding: 7bit From: Phillip Hunt Mime-Version: 1.0 (1.0) Date: Tue, 20 Oct 2020 12:54:07 -0700 Message-Id: <578EC62F-F4EC-482F-A44F-C0AB3C38A024@independentid.com> References: Cc: scim@ietf.org In-Reply-To: To: "Karaimin, Aleyidin" X-Mailer: iPhone Mail (18A393) Archived-At: Subject: Re: [scim] Extend core schema multivalue complex attribute X-BeenThere: scim@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Simple Cloud Identity Management BOF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2020 19:54:13 -0000 --Apple-Mail-5D442460-2021-4B87-A7A7-696354327F37 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Aleyidin At present there is no way to do this. :-( Best way I have seen is to move the whole CMVA attribute to the extension.=20= Splitting attributes across schemas will like break most parsers as this is n= ot expected.=20 Extending existing complex attributes is well worth discussing in the scim.n= ext discussion. Being able to add sub-attributes like =E2=80=9Cverified=E2=80= =9D is very useful.=20 Another solution might be simply to add the new attribute to your core User s= chema definition. You won=E2=80=99t be running 100% standard schema but at l= ease your schemas endpoint would be discoverable and clients can understand t= he new attribute definition there. Clients that don=E2=80=99t read the sche= mas will likely just ignore the attribute...which in many cases is fine sinc= e they don=E2=80=99t understand it anyway.=20 There are also many cases where a scim endpoint does not support the full st= andard schema. SCIM clients in general should expect some deployment differ= ences which can be uncovered by looking at actual schema definition at the s= chemas endpoint.=20 At the very least a best practice document from the group would be helpful.=20= Phil > On Oct 19, 2020, at 3:56 AM, Karaimin, Aleyidin wrote: >=20 > =EF=BB=BF > Hi > =20 > I would like to ask you for possible way to extend multivalue attribute. O= ur use cases require to support additional sub-attributes for some User and G= roups multivalue complex attributes. For example: > =20 > { > "schemas": [ > "urn:ietf:params:scim:schemas:core:2.0:User" > ], > "userName": "sample", > "emails": [ > { > "type": "work", > "value" "sample@example.com", > "otherAttribute": "value" // the name is k= nown (It is defined by us) > } > ] > } > =20 > According to spec, this will conflict with the core schema. I know that I c= ould define extension schema and add this attribute but this would lead to a= lot duplicate data. > =20 > { > "schemas": [ > "urn:ietf:params:scim:schemas:core:2.0:User" > ], > "userName": "sample", > "emails": [ > { > "type": "work", > "value" "sample@example.com", > ... > } > ], > "urn:ietf:params:scim:schemas:extension:enterprise:2.0:Emails" : { > "emails": [ > { > "type": "work", > "value" "sample@example.com", > "otherAttribute": "value" // the name is k= nown (It is defined by us) > ... > } > ] > } > } > =20 > My question is if there is another solution to achieve this. > Thank you. > =20 > Best Regards > Aleydin > _______________________________________________ > scim mailing list > scim@ietf.org > https://www.ietf.org/mailman/listinfo/scim --Apple-Mail-5D442460-2021-4B87-A7A7-696354327F37 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Aleyidin

At present ther= e is no way to do this. :-(

Best way I have seen is= to move the whole CMVA attribute to the extension. 

Splitting attributes across schemas will like break most parsers as t= his is not expected. 

Extending existing compl= ex attributes is well worth discussing in the scim.next discussion. Being ab= le to add sub-attributes like =E2=80=9Cverified=E2=80=9D is very useful.&nbs= p;

Another solution might be simply to add the new a= ttribute to your core User schema definition. You won=E2=80=99t be running 1= 00% standard schema but at lease your schemas endpoint would be discoverable= and clients can understand the new attribute definition there.  Client= s that don=E2=80=99t read the schemas will likely just ignore the attribute.= ..which in many cases is fine since they don=E2=80=99t understand it anyway.=  

There are also many cases where a scim endpo= int does not support the full standard schema.  SCIM clients in general= should expect some deployment differences which can be uncovered by looking= at actual schema definition at the schemas endpoint. 

At the very least a best practice document from the group would be h= elpful. 

Phil

=
On Oct 19, 2020, at 3:56 AM, Karaimin, Aleyidin &l= t;aleyidin.karaimin@sap.com> wrote:

=EF=BB=BF =

Hi

 

I would like to ask you for possible way to extend mu= ltivalue attribute. Our use cases require to support additional sub-attributes for some User and Groups multivalue complex attributes. = For example:

 

{

         = ;       "schemas": [

        "urn:ietf:= params:scim:schemas:core:2.0:User"

    ],

    "userName": "sample",

    "emails": [

         &nbs= p;      {

         &nbs= p;            &n= bsp;         "type": "work",

         &nbs= p;            &n= bsp;         "value" "sample@example= .com",

         &nbs= p;            &n= bsp;         "otherAttribute": "valu= e" // the name is known (It is defined by us)

         &nbs= p;      }

    ]

}

 

According to spec, this will conflict with the core s= chema. I know that I could define extension schema and add this attribute bu= t this would lead to a lot duplicate data.

 

{

         = ;       "schemas": [

        "urn:ietf:= params:scim:schemas:core:2.0:User"

    ],

    "userName": "sample",

    "emails": [

         &nbs= p;      {

         &nbs= p;            &n= bsp;         "type": "work",

         &nbs= p;            &n= bsp;         "value" "sample@example= .com",

         &nbs= p;            &n= bsp;         ...

         &nbs= p;      }

    ],

    "urn:ietf:params:scim:schemas:exte= nsion:enterprise:2.0:Emails" : {

         &nbs= p;      "emails": [

         &nbs= p;      {

         &nbs= p;            &n= bsp;         "type": "work",

         &nbs= p;            &n= bsp;         "value" "sample@example= .com",

         &nbs= p;            &n= bsp;         "otherAttribute": "valu= e" // the name is known (It is defined by us)

         &nbs= p;            &n= bsp;         ...

         &nbs= p;      }

    ]

    }

}

 

My question is if there is another solution to achieve this.

Thank you.

 

Best Regards

Aleydin

_______________________________________________
scim m= ailing list
scim@ietf.org
https://www.ietf.o= rg/mailman/listinfo/scim
= --Apple-Mail-5D442460-2021-4B87-A7A7-696354327F37--