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

Sathya Bandara <sathya@wso2.com> Wed, 18 April 2018 15:44 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 7E7C31243F3 for <scim@ietfa.amsl.com>; Wed, 18 Apr 2018 08:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 sWqnh9JpNJJu for <scim@ietfa.amsl.com>; Wed, 18 Apr 2018 08:44:57 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (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 DD27A120727 for <scim@ietf.org>; Wed, 18 Apr 2018 08:44:56 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id v64-v6so2412941otb.13 for <scim@ietf.org>; Wed, 18 Apr 2018 08:44:56 -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=woAMyHLUDPgGR/XyctFHIX5NOsajM9oD4t+C+fTwUFE=; b=Kk2ar7pU08qszIHdBOYmh5LiRtnJapNbKO6FMWGyGH1rWPoIXF+S7qYiv7rEYbry1a PYLOF2p/ypSH6fBgLyIIvCFlzqkLq9kdPj5eaV9+KYgR5UZTYQL7awtDZnYEVD8S4k4j 5NhIlxTkNwhkwbtbsCHPLuCN96mxCD4WLm+cA=
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=woAMyHLUDPgGR/XyctFHIX5NOsajM9oD4t+C+fTwUFE=; b=rfWfF5k0NQpKECk61cxuwhQIocE0BTcrdWQe5hdw1hWrPGCqY1aSAvX3hgMVYTIS2s lVfumkbD0auvUOqMtUJnJqPgRhL7CzfGJW5i2wM0GEmuAuelFqI3HgDfMNMOkPKyDUR+ Vvi7psNKavZEOxg/SdknsU6LirhtaEtPS9J/+YV5mqPQOmZVDII1GJZA4gSrJthv4u0n R7/6uyuJWuuu8uj71ggurNn1CcVBwTuTvSLHvTKHgTi8P+4S5I5CyMIJoQOMlwn1Q+nb dYHbBoOo4wjP1R12g4SXxR9rEQrhtzLCzXek23a44Aa7xI4hornVJC0MbrakoVrSuziv KXxw==
X-Gm-Message-State: ALQs6tD3XeBX2jNIP5XtOcw5M7d+8pBagbAblK1UcEyZWJlT4R4srAbT dSRUF2z++czVdYiOiTJvksUhdRY0x/QeIjM29G7Fyg==
X-Google-Smtp-Source: AIpwx49/HrQsRyHaV5Wuf62fN+HlX+kEiyLpBU6TxP0eJIhpwShKM9cGo6OQTjPf/oekiGsUN6+ViI1UH7eaZHKmXzA=
X-Received: by 2002:a9d:509:: with SMTP id 9-v6mr1715539otw.342.1524066296237; Wed, 18 Apr 2018 08:44:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAAdTB9Ey5xGfb=xcn19=NTdtJg_Td_z3qXjUfg=F28F93BY7BQ@mail.gmail.com> <BN7PR04MB38899330C8CE63EDF2EA5DF5E2B60@BN7PR04MB3889.namprd04.prod.outlook.com>
In-Reply-To: <BN7PR04MB38899330C8CE63EDF2EA5DF5E2B60@BN7PR04MB3889.namprd04.prod.outlook.com>
From: Sathya Bandara <sathya@wso2.com>
Date: Wed, 18 Apr 2018 15:44:45 +0000
Message-ID: <CAAdTB9HqWZ_jP0s4hOY1kjEMMkf9gzaPEJfT-pCibmaa=R+02g@mail.gmail.com>
To: Kelly Grizzle <kelly.grizzle@sailpoint.com>
Cc: scim@ietf.org
Content-Type: multipart/alternative; boundary="00000000000033a85a056a21566f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/eRIeojsZ7BaO1FyF7vO_IsjQhPY>
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 15:44:59 -0000

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
>
> Best regards,
>
> Sathya
>
>
> --
>
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
>
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
>
>