MIME-Version: 1.0
From: Matthew De Haast <matt@coil.com>
Date: Thu, 14 May 2020 11:04:50 +0200
Message-ID: <CANsTMfEmmF6jBdgWAZtpycHFfO9RDeKN=VojEMiZP1O2pXZ-sA@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e9caf505a597fd0b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Yh2K8Phf9cHlxbNuuClx9sz7Noc>
Subject: [OAUTH-WG] RAR - Client Credentials and Authorization Details
Precedence: list

--000000000000e9caf505a597fd0b
Content-Type: text/plain; charset="UTF-8"

RFC6749 allows scopes to be presented at the token endpoint for cases like
client credentials grants.

It's not clear how this could be achieved with the current RAR spec though
when a Client using Client Credentials wants to request fine grained access
using authorization_details. Or should this even be possible?

Matt

--000000000000e9caf505a597fd0b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>RFC6749 allows scopes to be presented at the token en=
dpoint for cases like client credentials grants.<br></div><div><br></div><d=
iv>It&#39;s not clear how this could be achieved with the current RAR spec =
though when a Client using Client Credentials wants to request fine grained=
 access using authorization_details. Or should this even be possible?</div>=
<div><br></div><div>Matt<br></div><div></div><div><br></div></div>

--000000000000e9caf505a597fd0b--