[scim] Query parameter to include attributes in result that are not returned by default
Aleksey Chernoraenko <achernoraenko@gmail.com> Wed, 10 April 2019 16:38 UTC
Return-Path: <achernoraenko@gmail.com>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F271203BA for <scim@ietfa.amsl.com>; Wed, 10 Apr 2019 09:38:22 -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, FREEMAIL_FROM=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 (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 Dh7Il5UItGdG for <scim@ietfa.amsl.com>; Wed, 10 Apr 2019 09:38:20 -0700 (PDT)
Received: from mail-oi1-x22f.google.com (mail-oi1-x22f.google.com [IPv6:2607:f8b0:4864:20::22f]) (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 75B3112037D for <scim@ietf.org>; Wed, 10 Apr 2019 09:38:20 -0700 (PDT)
Received: by mail-oi1-x22f.google.com with SMTP id a6so2334953oie.5 for <scim@ietf.org>; Wed, 10 Apr 2019 09:38:20 -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=I+be+3XZajAlHARt9A507a2ufDEvARIc3S1TYtLyNag=; b=KR1WX8JaLdUjDRi+T09jkuH+mdsev4JdHVno/dCHoOMSiLS39+qEAPDFEL7mHQQacO Vh+xSNTNgLHsMVDUztwECKpPdQovT8MqXVela2CAsNGvEJpIcwQFdsLNYbKERLDnzP6w +qh//eAZaXUFtah86uCkfIYTCulhtmbV7eCUEuXgJqCucZOj2itDT6MkJl3fJI+mDt8Y e4kdyRdpnccjxUVzQ/kFh0WwiYnUJENhOVdHh8/NeIKelkR385ogy+V3/KhrIPI1Fitw Ee2CmPdZOs7nTZWgDIcxWWaeK3eh2O15j2jKJsR5s8FVx4DMUEFc5rf0E4oy0b2N7FPg rN5w==
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=I+be+3XZajAlHARt9A507a2ufDEvARIc3S1TYtLyNag=; b=djjpFRlobx3fGBr1gcxP4GH3O1xJ8L6Vnl7xZpXNWZwbyBGmHHriEDtoYiwsIu3AP1 QhrrvQwvgOPa63To3qiUx8RW9FXCPaFzqxczDkW87vvuGknNfSPdedOOheNy2sxTe2+W g4jNE2njrHqQUyzG44tEYKo44k5QV1Rx9WpmxKFhUspz9yy4BqOnPODPoEm/W/xtUeuI Flshk0gXg6AE21Zo43ZRZJCuYPebEqwZgXsiySIfZ9tqlRKNu/MOVgIxy2lQOGVP+wg7 8HuOWI5fyWjctIz49T8fxmVwsZ8f83NYpkI7c3Bb9xgXlQYjzInO0t9VCgo6O158znWy bxag==
X-Gm-Message-State: APjAAAUScZ15L53zizKAy6wKBgmeC/QSIBXMUkxnTzBKi4/uUARMJWj2 XkYoUHPgzmAzGyBpKYG8NAJkuGonP4XvUnckW4ha7g==
X-Google-Smtp-Source: APXvYqyI0y2/C4QgbM4og3VI8lUOLOn+cQXnT9eryo2gSeEJR1jMoS2skeKDH1R+knpdRNG4XZRUl7TAOIBWD0TD/3s=
X-Received: by 2002:aca:b984:: with SMTP id j126mr3267881oif.113.1554914299485; Wed, 10 Apr 2019 09:38:19 -0700 (PDT)
MIME-Version: 1.0
From: Aleksey Chernoraenko <achernoraenko@gmail.com>
Date: Wed, 10 Apr 2019 11:38:08 -0500
Message-ID: <CAKCnT7xOPMf3214wO249Yf_Sy91c6izJunvp0v=iyn3eAyJvCQ@mail.gmail.com>
To: scim@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/scim/0bOXGvNW73snBQCtK9N7sVJO7Ts>
Subject: [scim] Query parameter to include attributes in result that are not returned by default
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 16:38:22 -0000
Greetings,
"attributes" and "excludedAttributes" query parameters as described in
3.4.3. section of rfc7644 allow to support at least two scenarios
1) when requestor wants to exclude attributes that are returned by
default (e.g. expensive, or "not interested in" ones, etc)
2) when requestor wants to get a specific set of attributes and by
that overrides defaults
but it looks like another valuable scenario is missing:
3) when requestor wants to include attributes that are not returned by
default ("returned" schema attribute would be "request" for such
attributes) without discarding the defaults of other attributes.
Would introducing "includedAttributes" parameter be a good idea?
Any thoughts?
Thanks,
Alexei
- [scim] Query parameter to include attributes in r… Aleksey Chernoraenko
- Re: [scim] Query parameter to include attributes … Phil Hunt