[scim] Where are arbitrary fields allowed in a SCIM resource?
"Moyer, Steven William" <smoyer@psu.edu> Thu, 02 April 2020 13:48 UTC
Return-Path: <smoyer@psu.edu>
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 8CFE13A131A for <scim@ietfa.amsl.com>; Thu, 2 Apr 2020 06:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pennstateoffice365.onmicrosoft.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 0QCrUwFBFDCP for <scim@ietfa.amsl.com>; Thu, 2 Apr 2020 06:48:47 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0726.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::726]) (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 186313A12F2 for <scim@ietf.org>; Thu, 2 Apr 2020 06:48:45 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HzCFNhyhIn0Grplh6jjznlmnzZdGbYUU3ppm5swhAIf0JJaRZ/ilr8UK3hsnOZt6qy6IZjndwKHKAtYI7k09hr3yLV7xg3I6W0kcowNWzv0srTdOxLOOqWJZCvKPMSxHq0p/Jnc8ZQYjQbq7RH9BcVUEjwqHWHPVQt/o2RZqFyQgZKYnEUCBu2CZuQGx4tlyS5UdQg1Ekk8J9ec4rvkg8fV65g9VRZpND4vcj/sbFS+pYDuJGK0z/NFdd2rc/mPlvRkO/QS6zvbwnMfPH1tJFrZrEmhenz3O+BjF7Stg/LLJy9GSzmndkD2rllkFgHYPscSnz3E9H77r+WRKtWQADw==
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=0BUfMU0BcBKucph+LmHQhbSqyNFLXnoqU/9i/y7shqc=; b=UVnMnXOdds07hG2NKlmsFq7DZkqKrrw1PRmurXFUkDwJ/HtnmHvDSHe9v5NqvS9yMA+4zmvsIghrkh3ecwdyKWIf1AhIfre4iFWlM3/mo+98vnRYiz5t1uHiJtbPSi3ysTZIsJRDEDU/m2FOZ+CWB2RFVW9ZLAIJJQZQ+1R8C9+i3PW+WNocucMvPIIc7OmgQTHDJYLA3qUmNgXIfayQgu0xuW5v4er3NOXbgYIdhxuyd3GqdrKBGHB/45knq/i2VrCJuNk7yjZU0gnIXgrJIja0GlGoShE64MWL6XG8G5ZgGZRha8GjyKD+dUBgy1W/9cg/8Q/OrjNO7/uFrCBo6g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=psu.edu; dmarc=pass action=none header.from=psu.edu; dkim=pass header.d=psu.edu; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=PennStateOffice365.onmicrosoft.com; s=selector2-PennStateOffice365-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0BUfMU0BcBKucph+LmHQhbSqyNFLXnoqU/9i/y7shqc=; b=VB+umitirrriBV+2Ky41+nu1sq2AB5aEPxuZ1MLb5H40CViu9me0xvuJh8ezwsvjOy0+3a8q9Q7jhWRiyGGFTvlyfSlO+jhbrJZZE05pNYmJzuIpqQMpmJva+kAnaz2ssDJWFAe3TkSK8rEat7rDc+bnwmiaIfLhnDnfUknLqvw=
Received: from CH2PR02MB6262.namprd02.prod.outlook.com (2603:10b6:610:8::12) by CH2PR02MB6917.namprd02.prod.outlook.com (2603:10b6:610:88::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.18; Thu, 2 Apr 2020 13:48:44 +0000
Received: from CH2PR02MB6262.namprd02.prod.outlook.com ([fe80::1d48:8fd5:f340:aff1]) by CH2PR02MB6262.namprd02.prod.outlook.com ([fe80::1d48:8fd5:f340:aff1%7]) with mapi id 15.20.2856.019; Thu, 2 Apr 2020 13:48:44 +0000
From: "Moyer, Steven William" <smoyer@psu.edu>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: Where are arbitrary fields allowed in a SCIM resource?
Thread-Index: AQHWCPVnIdjezxY9XU6jQUm1m4NZMA==
Date: Thu, 02 Apr 2020 13:48:44 +0000
Message-ID: <CH2PR02MB6262CC3CFC89A33627077A70C9C60@CH2PR02MB6262.namprd02.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=smoyer@psu.edu;
x-originating-ip: [71.58.212.108]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5c46499e-c205-4f49-965a-08d7d70c8fa7
x-ms-traffictypediagnostic: CH2PR02MB6917:
x-microsoft-antispam-prvs: <CH2PR02MB69170034F2F299A723EB2FC2C9C60@CH2PR02MB6917.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0361212EA8
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CH2PR02MB6262.namprd02.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(10019020)(4636009)(376002)(346002)(39860400002)(366004)(396003)(136003)(75432002)(76116006)(66946007)(86362001)(66476007)(186003)(71200400001)(9686003)(55016002)(7696005)(5660300002)(8676002)(19627405001)(6506007)(66556008)(4744005)(316002)(33656002)(81166006)(2906002)(81156014)(6916009)(786003)(478600001)(64756008)(8936002)(52536014)(66446008)(26005); DIR:OUT; SFP:1102;
received-spf: None (protection.outlook.com: psu.edu does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: YD06XtJw7hkxeTR/Se0QW9cNrhUXZd6Rum+GhiiBTqKH5ujGJLJ72+CXxP9WaKXJe8MYJkPZE9dxR4lvB+ZvW+dznGafYq2aKtk+gGYRyWZi63QNRHok4VN/47t0RgvUwV7lgzfEnl+NQ7CPMczeCQwBATynIDtu1YJOHNJORoX7DsJKovots6HfWY3ukECiK6Y7u7tln8dpAi4zDDLbmT5A7OKRe66m4llE1XgfCqrytLC4K1qr9t7Todpr1VaMPE20QbECFmZbF6yrnyJWKbmDNmUHA3fm4+w4c0J0EhtX57iVD4+PwTQJZruqrp5pAJgkFw+hXBR3HfUIF1L89tKjHY5Lw9fPAy1I8zRNcIUDxOBeGpIfLPJJnYfk0fosAHF0nt0XuUPWq/t5lct0mu5bUvoRy/JdRe84F51VuN6n1hUIAfcu0YuMKi1o3g+e
x-ms-exchange-antispam-messagedata: VUy5vvf/3mR5F8zyYrvUXxWit8gOzJCFqAXTazo3OVrm4r+6uPAHSiF+ArmhfK2szyZCXovq0iENeh5phuIyR3k+QfsI1/Ul4xzUFI3JRKdzTB/pnxAJe/TgEX+QkH9EUByjg1hkiFe93g4QwJ3OGg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR02MB6262CC3CFC89A33627077A70C9C60CH2PR02MB6262namp_"
MIME-Version: 1.0
X-OriginatorOrg: psu.edu
X-MS-Exchange-CrossTenant-Network-Message-Id: 5c46499e-c205-4f49-965a-08d7d70c8fa7
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Apr 2020 13:48:44.4629 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 7cf48d45-3ddb-4389-a9c1-c115526eb52e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bhWIUNEdwvHw2y6xz40471xXOfDvz96kfs0ibdts6IrvZrM7ktd5SmXSYPbHcVzn
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR02MB6917
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/XeP-QWBsNgHAyA8SA-bBlVCHRn4>
Subject: [scim] Where are arbitrary fields allowed in a SCIM resource?
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2020 13:48:54 -0000
When SCIM resources are represented as JSON objects, the specification is pretty clear that arbitrary fields are allowed in the top-level JSON object but a question has come up related to arbitrary fields within complex objects. We need additional information in the SCIM Address type and would rather embed the attributes than reference extension data. Thanks, Steve
- [scim] Where are arbitrary fields allowed in a SC… Moyer, Steven William
- Re: [scim] Where are arbitrary fields allowed in … Phillip Hunt