IETF Logo Mail Archive

Re: [OAUTH-WG] RAR & multiple resources?

Dick Hardt <dick.hardt@gmail.com> Tue, 14 January 2020 05:08 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 B4C9D12001E for <oauth@ietfa.amsl.com>; Mon, 13 Jan 2020 21:08:59 -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 ogXltN10ZnaF for <oauth@ietfa.amsl.com>; Mon, 13 Jan 2020 21:08:58 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 E505A120019 for <oauth@ietf.org>; Mon, 13 Jan 2020 21:08:57 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id z22so12805658ljg.1 for <oauth@ietf.org>; Mon, 13 Jan 2020 21:08:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ny8mABINk+9UjwvwgenYI44Jhxdtym//dXEw0XYWFJk=; b=actxzOGujXZOARreT2FPK97z4AdFBgrebw1iwJk4209zmMdBDjA/kp+wO3ZsMhZBpa EpnOZvCvA30t0Fk1KOkItq4YRHk54ViKgdyfrwOzsiTIhR6Fma/1h9I3dLHfhZRqMkt/ 1TQku6xfmBFA3aUwZTRXyUeDqKaDwNJlgUn7ePMGykNscnUUhXRPb291LrFyZNpO8R9l yOy/Sk7XZJ6SBw4QwBPZ+zjS1bBX9VyeNpY2nod2O1DY2XWknRKSuCRJmqF5OgV7Ag9H FAQ2Yy6kY/bi4kePMdozm0+5f3tO4Zt+NizTKj+Akoco/N2wGkYayerXSAWBB+xsCyZL mIaw==
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=Ny8mABINk+9UjwvwgenYI44Jhxdtym//dXEw0XYWFJk=; b=EoK3fe8FZS/fXLsKTNsut7mzl9mHH0Nx828OkIXdb9Gt1AET8EbLXhM3LFVJPgvFwn 79y/bJuKbCkkq/cJHLmxsRZ2JxGgaDZedrbNf3YIq+1KG8bTh4Xio1/4FRFU9BUJKrCh L5J5z9cjtOYpPqPMLzMh1muNSLmBy0XXnThXrqJvhR5TqUhGfzAacR23iZb3gvtpa0AL E6hvw09FlxaL0tQ2mleQMvAz3c2H9mr6QkYb2W+lMCYrqgkaIcK6X35Bl8BSLK4X1yF0 hwmlQWs9YeJhF3uPE0EzZNqXJDVo1EdgICtYYQWj1cofoXH0phRjdmClEtVSNAb1n5Xi Mn6Q==
X-Gm-Message-State: APjAAAWZtTK7nuYBZrOCJ7p6vFB4iqRYczo8exkfWheGDKrPsv64I3NU dXYxkBv3N4xqPudDfwBgjAZmDv+NCuNl64J956g=
X-Google-Smtp-Source: APXvYqxDwFwVgQbEwKU2fJ0paqVGU/HKi+P967pOF3QJKdzE617Wo+3HOG2UpwOyFyzBg9bFtjtNtYeNpecXjZ4z2LU=
X-Received: by 2002:a2e:9e4c:: with SMTP id g12mr12971445ljk.15.1578978536205; Mon, 13 Jan 2020 21:08:56 -0800 (PST)
MIME-Version: 1.0
References: <CAD9ie-uEuvWv4Z1y-+JcebWcX69UMTN2ZNOQKWiQVOa=j8wtVg@mail.gmail.com> <11D44A57-1255-4DDB-807E-7E2DE7A47B74@mit.edu>
In-Reply-To: <11D44A57-1255-4DDB-807E-7E2DE7A47B74@mit.edu>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 13 Jan 2020 21:08:44 -0800
Message-ID: <CAD9ie-ti088S+YZ4Ybq7VBzyQ2Ed7Tyaua_M1tiiiHoU9r7QsA@mail.gmail.com>
To: Justin Richer <jricher@mit.edu>
Cc: Brian Campbell <bcampbell@pingidentity.com>, Torsten Lodderstedt <torsten@lodderstedt.net>, oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c23011059c1296c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/dv0HQ0O2oP_kQykEWSBxI6GH0q8>
Subject: Re: [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 05:09:00 -0000

That’s what I thought. Thanks for the clarification.

On Mon, Jan 13, 2020 at 6:20 PM Justin Richer <jricher@mit.edu> wrote:

> Multiple access tokens are outside the scope of RAR. The request is
> intended to describe the access for a single returned access token. If
> semantics for multiple access tokens are agreed upon, then it can use the
> RAR structure, the Resources parameter, and the Scope parameter all in
> parallel again.
>
>  — Justin
>
> > On Jan 13, 2020, at 8:31 PM, Dick Hardt <dick.hardt@gmail.com> wrote:
> >
> > 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
>
>

v2.23.0 | Report a Bug | By Email