Re: [scim] Is it possible to use primitive types with SCIM addresses claim?

Sathya Bandara <sathya@wso2.com> Wed, 18 April 2018 17:24 UTC

Return-Path: <sathya@wso2.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 BC8FA12D881 for <scim@ietfa.amsl.com>; Wed, 18 Apr 2018 10:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wso2.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 zw-Qd3cjLcss for <scim@ietfa.amsl.com>; Wed, 18 Apr 2018 10:24:53 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 6884A126D85 for <scim@ietf.org>; Wed, 18 Apr 2018 10:24:53 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id y46-v6so2796230otd.4 for <scim@ietf.org>; Wed, 18 Apr 2018 10:24:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zwy9L6i+2oIM2GGF/5OadHOFaMAA60yJFdtAnrKwVF8=; b=T7JvuJ6gvO+XMKEQ2Vy94WO/soxVDrLIeurycSTJ5Zk7JRlMgsjcFgE6uHEbrjIGw2 9s6K/CzjpoXUEwEFLxgvu/NjFwdxhlxKftMsAXSAmpsOmrgZApkhPAsufJ8yHIsLGBTc erYWN12p32mXVtCIc513jroChH5qC88CM2+e0=
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=zwy9L6i+2oIM2GGF/5OadHOFaMAA60yJFdtAnrKwVF8=; b=CFx/A+DYIZeOJJW3u4Mj3qFBEiiX/YQCOlIeEmAErADKr6qyGjOA40HpBsxJr8xLLn DJBCPD/CmWy56ZIGO0DsK3KBk5wH4HOcAgm+7/MEof791Pb0HNG1slVesAgLrXKYoLLK Mf7VLlmVRJQwyYSbQ4l8iM+ibNKXnZfcAGRFFm0U/s9kxRsfMgyr+1b2kow7bLicN9dm Z018/nJ8YUhKnwIQFzo8pMRKS59a4VdZZfSliIykYrnxKLFfToCgeqfiDIKgxOLtd+rd llPsGAs10wBHau9qtdl1IlNxnIDfUoQp/AJ+RAMAtepQoYMY+w5+wRTFke7taAytfc1M XSIw==
X-Gm-Message-State: ALQs6tC0PRWDK8d6WZ5nMj4PBGh1Q6eBlGl/G8vDFPQRToD1tLntncaF u/yZ2y7WjQPHUDKvxmDNmxszoh4+Yd8psSY6Tmv2SA==
X-Google-Smtp-Source: AIpwx4+uwQz1GS9TZkkbNtY1rCPuNhFSP9qfN4Ox7sKI5J95weLMvroFRhs/vtcCImWCQuV2SdLQDaR3D5EUpd+TpxE=
X-Received: by 2002:a9d:4ee:: with SMTP id 101-v6mr1726356otm.122.1524072292761; Wed, 18 Apr 2018 10:24:52 -0700 (PDT)
MIME-Version: 1.0
References: <CAAdTB9Ey5xGfb=xcn19=NTdtJg_Td_z3qXjUfg=F28F93BY7BQ@mail.gmail.com> <BN7PR04MB38899330C8CE63EDF2EA5DF5E2B60@BN7PR04MB3889.namprd04.prod.outlook.com> <CAAdTB9HqWZ_jP0s4hOY1kjEMMkf9gzaPEJfT-pCibmaa=R+02g@mail.gmail.com> <42363E44-201A-4370-9E79-E1B38158C3B1@oracle.com> <CD4E026C-5DF9-4AAD-B0F2-C34992CEDCD8@oracle.com>
In-Reply-To: <CD4E026C-5DF9-4AAD-B0F2-C34992CEDCD8@oracle.com>
From: Sathya Bandara <sathya@wso2.com>
Date: Wed, 18 Apr 2018 17:24:42 +0000
Message-ID: <CAAdTB9HmOt6Xrb0viV2z1rL_7+Kb7dv8VESAwYyTUL_OtF_J8w@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Cc: scim@ietf.org, Kelly Grizzle <kelly.grizzle@sailpoint.com>
Content-Type: multipart/alternative; boundary="0000000000009f5d41056a22bb48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/9AngXOHmLpyq4X5Xr9nwWJKomDg>
Subject: Re: [scim] Is it possible to use primitive types with SCIM addresses claim?
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.22
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 Apr 2018 17:24:57 -0000

Thank you Phil, for the clarification.

Best regards,
Sathya

On Wed, Apr 18, 2018, 10:14 PM Phil Hunt <phil.hunt@oracle.com> wrote:

> To clarify that was “yes” as in it would violate the schema.
>
> Phil
>
> Oracle Corporation, Identity Cloud Services Architect
> @independentid
> www.independentid.com
> phil.hunt@oracle.com
>
> On Apr 18, 2018, at 9:36 AM, Phil Hunt <phil.hunt@oracle.com> wrote:
>
> Yes. The expectation is for some consistency in presentation across
> implementations.
>
> So if you are mapping LDAP data, you have to parse the address value into
> the sub-attributes for addresses in SCIM.
>
> Phil
>
> Oracle Corporation, Identity Cloud Services Architect
> @independentid
> www.independentid.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.independentid.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=K6UEQCIxf3e1RlkBwJAmc0so58P9Li0dZnNgGTcSUQ4&s=rScN-d7CjGqHWE0iYfsWh8-NKNBq5Lrm4ooaVr3DQU4&e=>
> phil.hunt@oracle.com
>
> On Apr 18, 2018, at 8:44 AM, Sathya Bandara <sathya@wso2.com> wrote:
>
> Hi Kelly,
>
> Thanks for the quick response.
> So if we allow primitive types as well, in addition to complex types for
> the addresses claim from server side, would it violate the schema?
>
>
> On Wed, Apr 18, 2018, 7:17 PM Kelly Grizzle <kelly.grizzle@sailpoint.com>
> wrote:
>
>> This is likely to break other clients/servers that expect a multi-valued
>> complex object.  I would suggest using a schema extension that has a list
>> of primitives.  Another option would be to use the standard addresses
>> field, but only include the “formatted” sub-attribute.
>>
>>
>>
>>
>>
>> *From:* scim <scim-bounces@ietf.org> *On Behalf Of *Sathya Bandara
>> *Sent:* Wednesday, April 18, 2018 8:09 AM
>> *To:* scim@ietf.org
>> *Subject:* [scim] Is it possible to use primitive types with SCIM
>> addresses claim?
>>
>>
>>
>> Hi,
>>
>> As per the SCIM core schema specification [1], addresses claim definition
>> is as follows.
>>
>> addresses
>>
>>       A physical mailing address for this user.  Canonical type values
>>
>>       of "work", "home", and "other".  This attribute is a complex type
>>
>>       with the following sub-attributes.  All sub-attributes are
>>
>>       OPTIONAL.
>>
>> In a scenario where all the sub-attributes can be empty as per above
>> definition, can we use primitive attribute types (string values) as the
>> claim-values for this claim. E..g. -  *addresses: ["address1",
>> "address2"]*
>>
>> Would be grateful if you could clarify whether this is possible.
>>
>> [1] https://tools.ietf.org/html/rfc7643#section-4.1..2
>>
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7643-23section-2D4.1.2&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=BiPVo8BLSRchQq0X5X8fTO2Sc7XlO9d4vnvrMJ9immA&s=7e1irqMvgYOZIoQ9yOV21JO5A5HG_dDXUI-Udjpo5NI&e=>
>>
>> Best regards,
>>
>> Sathya
>>
>>
>> --
>>
>> Sathya Bandara
>> Software Engineer
>> WSO2 Inc. http://wso2.com
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__wso2.com&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=BiPVo8BLSRchQq0X5X8fTO2Sc7XlO9d4vnvrMJ9immA&s=IFRilCcF6Ve_ZSRufegaA_-VJ9NtyRqavRA7ymgOQjo&e=>
>>
>> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>>
>>
>> _______________________________________________
> scim mailing list
> scim@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf..org_mailman_listinfo_scim&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=BiPVo8BLSRchQq0X5X8fTO2Sc7XlO9d4vnvrMJ9immA&s=MGbT_IyCqPu-X2yNNe4Oge4LN28CoFDhjAa2pKZvFAE&e=
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_scim&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=BiPVo8BLSRchQq0X5X8fTO2Sc7XlO9d4vnvrMJ9immA&s=MGbT_IyCqPu-X2yNNe4Oge4LN28CoFDhjAa2pKZvFAE&e=>
>
>
> _______________________________________________
> scim mailing list
> scim@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_scim&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=na5FVzBTWmanqWNy4DpctyXPpuYqPkAI1aLcLN4KZNA&m=K6UEQCIxf3e1RlkBwJAmc0so58P9Li0dZnNgGTcSUQ4&s=P7pirz7KGVgCVDLb0ds_tElr0yrM921L8jtIVtrue8k&e=
>
>
>