Re: [OAUTH-WG] RAR - Client Credentials and Authorization Details

Torsten Lodderstedt <torsten@lodderstedt.net> Thu, 14 May 2020 10:09 UTC

Return-Path: <torsten@lodderstedt.net>
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 57CB83A0887 for <oauth@ietfa.amsl.com>; Thu, 14 May 2020 03:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lodderstedt.net
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 0k4GsNzMpOlN for <oauth@ietfa.amsl.com>; Thu, 14 May 2020 03:09:51 -0700 (PDT)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 A695D3A07A4 for <oauth@ietf.org>; Thu, 14 May 2020 03:09:50 -0700 (PDT)
Received: by mail-wr1-x431.google.com with SMTP id i15so3094168wrx.10 for <oauth@ietf.org>; Thu, 14 May 2020 03:09:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hBXuc5GWGwZBaBbfuuVFKcSDXnpuhnOozCHERPTk3CM=; b=ccfcJGBXrZmHUxhNTIQ8tnT0UjRobdlRUkMHAEl4JRK9XwiA5uDIdoNSWcP/0Ks84q Bo154gtvOYxOj7++B6mOWLeaKNOSqo8kTt5uRkhZkBFK28ul5nUaKo3ka2aXsN6iXD4y MhB082u2ZUubF87MEXwxMsN+CVjDuENjO+nTNpPGM2wfE50G9Ir7KXOTDW6ydMfEbQwO Wo6wj26z1bpKS5hKuuj4hkmdEE4oPyG4N3bZMn4a4HXvI7BU3erwRk0bwYyvAaGM40q4 dU/u8bpthPC2VLA0qE37yh/8boqfgqrbzosPLPpVgHCUmUBomMkKjburYsJpV50sQuwM AIdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hBXuc5GWGwZBaBbfuuVFKcSDXnpuhnOozCHERPTk3CM=; b=fasnG58V10ze7oPiKb5z5+cbnR5xr2vvGAPC0YlJKaxse8v2KpwMvUS8bmIbQLzLh+ ZKsIwn4bOeDWhIMdODSKutEg+3wUJAFFpcjyzD3zJ7T7/cGDmg1p7gxgi/0BLDFTSq0J OZaBrA93HcuLbrDcMEDgGS5nhZdgpjNN7tFrBNA/Wt7VLkY/m8yEv2X0z3yrH5pFHm4f +cRsHn2zdChaAK3dn96M6y4Ra3sknBnZalUxW+jBJt7w4Uy3xuxOqlUfF9RyIzzqAQci Kqiqhug9YWzsxnoQ5Gbz0avbhPw1G5V/RV3DJ+Wh7zTqYaqorIzsuvCTw7q5Y/OHuXnp Fapw==
X-Gm-Message-State: AOAM533ZuiTH0TnhARrL1s5GsPYbqvFOK4bhJTUUQQzXft81+JR2OmDz fxTHn8agwkYImoqQTGawb+1hbfSy0Kc=
X-Google-Smtp-Source: ABdhPJyIKaGfVo9zB8ib1mN13Nq5KwdUkMu2FbWDR/xlPmKlMso4tC64TAYB5LgpeoFB1iS1W82T8w==
X-Received: by 2002:a5d:448e:: with SMTP id j14mr4464436wrq.261.1589450988821; Thu, 14 May 2020 03:09:48 -0700 (PDT)
Received: from p200300eb8f301f8b1d4993d41b246345.dip0.t-ipconnect.de (p200300EB8F301F8B1D4993D41B246345.dip0.t-ipconnect.de. [2003:eb:8f30:1f8b:1d49:93d4:1b24:6345]) by smtp.gmail.com with ESMTPSA id x184sm6621890wmg.38.2020.05.14.03.09.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 03:09:48 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Torsten Lodderstedt <torsten@lodderstedt.net>
In-Reply-To: <CANsTMfEmmF6jBdgWAZtpycHFfO9RDeKN=VojEMiZP1O2pXZ-sA@mail.gmail.com>
Date: Thu, 14 May 2020 12:09:47 +0200
Cc: oauth <oauth@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BBA99B3-EE92-48D3-B838-5DDF171C013C@lodderstedt.net>
References: <CANsTMfEmmF6jBdgWAZtpycHFfO9RDeKN=VojEMiZP1O2pXZ-sA@mail.gmail.com>
To: Matthew De Haast <matt=40coil.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/8ja01yzdL9EWbwgeqm8u6sNAs74>
Subject: Re: [OAUTH-WG] RAR - Client Credentials and Authorization Details
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: Thu, 14 May 2020 10:09:52 -0000

Sure. That's possible. 

https://tools.ietf.org/html/draft-ietf-oauth-rar-01#section-3.1 states 

"The request parameter can be used to specify authorization
   requirements in all places where the "scope" parameter is used for
   the same purpose, examples include:

…

Access token requests as specified in [RFC6749], if also used as
      authorization requests, e.g. in the case of assertion grant types
      [RFC7521]”

I filed a ticket to also mention this in the token request section. 

> On 14. May 2020, at 11:04, Matthew De Haast <matt=40coil.com@dmarc.ietf.org> wrote:
> 
> 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
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth