[OAUTH-WG] RAR & multiple resources?

Dick Hardt <dick.hardt@gmail.com> Tue, 14 January 2020 01:31 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 814EA120020 for <oauth@ietfa.amsl.com>; Mon, 13 Jan 2020 17:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Tv6vqFywH5YY for <oauth@ietfa.amsl.com>; Mon, 13 Jan 2020 17:31:44 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 70F4E12001B for <oauth@ietf.org>; Mon, 13 Jan 2020 17:31:44 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id v201so8422766lfa.11 for <oauth@ietf.org>; Mon, 13 Jan 2020 17:31:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=rhAVeJaSxiz1Fh8VRLPT7OTP02facygatz4MXOSIa2A=; b=FuwzaH9RxkFiUz+5kWHfhOQcQDWi1fOjbFrGwapJaN1xtvWeosWHWhdBXO9woOQE/U sBqD5S0MYaY+bXXjvFwrBvl0+mCNIm7dsgjjhhBrYSy9fIH7BFQe95w/KftLKfowODYI NOiHiRuOIlTqyxWPFY4XAo29Q+eXnw3Kl/gNiEiGpqCkHrHj4Bc4DzqhJtN1SCCAlvsy skB/ONIpkeICnYPFl1RvdY5beY33aRfmKleGw8scIXegb26x22ME4fbPe9larNOyr1qv EkzPuNWSCOpF/uAsf30YZqKF9na35KcYfgCpt1HfnndphYSt9yzK4TkpxmsxXNq1ysox fi6Q==
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:cc; bh=rhAVeJaSxiz1Fh8VRLPT7OTP02facygatz4MXOSIa2A=; b=uNCmV/MdVPbkKRi5cMQExsfL1JJGngZ+pz982dYVlJJXYVZ+uLk43k1ONWqH/W+6N6 B3SbEHEQV1VMlMDGoKRfpaHGVPgpVHPX40/9B2alUyHtcUJwlgNbYh7ErhX4T7vzfg+x Agz2qxJVacvFzkSrkw7SQ/OWTOWDe6CzkoOY+sN3NoAZoMASq/2FOxHaA9+EJIBFx7H5 WUIdbjGEB5upMxIeQg+NQafs9h2mvPkSLCaQkUpLp8Re7Vt9ARCC9+cPFlJlOO5/p/OR FzZegsJUDdWUFUwBZoUvFBvnmLOevysc9NmV0jonpaEvVVvjih9IaCoPjHcikggdUJHG 006Q==
X-Gm-Message-State: APjAAAUSpIfz/t90PqhJA2nQvZ9UcuSa5Mm/IUYfzVYNa2k3fqZgQpDI sMjdc3eKhLWODr5BmkHLJXevynZovglCeqZWMoM=
X-Google-Smtp-Source: APXvYqz0+QpYvg6xBVBP2ofaEiIjTZg6Z+/EW9wHCRNCBDrjx7QQ5vn6lc0Cwd04DB69eT7OEV+HbhK2OO9RASGJV/Q=
X-Received: by 2002:a19:cb54:: with SMTP id b81mr180146lfg.188.1578965502597; Mon, 13 Jan 2020 17:31:42 -0800 (PST)
MIME-Version: 1.0
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 13 Jan 2020 17:31:31 -0800
Message-ID: <CAD9ie-uEuvWv4Z1y-+JcebWcX69UMTN2ZNOQKWiQVOa=j8wtVg@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>, Brian Campbell <bcampbell@pingidentity.com>, Justin Richer <jricher@mit.edu>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e51f79059c0f8d43"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/PbtqC6B5Lx8p5u4S6DNKJ9dQ2RM>
Subject: [OAUTH-WG] RAR & multiple resources?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2020 01:31:47 -0000

Torsten / Justin / Brian

In my reading of the ID, it appears that there is a request for just one
access token, and the authorization_details array lists one or more
resources that the one access token will provide access to. Correct?

I have heard anecdotally that there is interest in granting access to
multiple resources, and having multiple access tokens, which would enable
different components of a client to have different access tokens.

Do you consider multiple access tokens out of scope of RAR?

/Dick