Re: [OAUTH-WG] updated Distributed OAuth ID

Dick Hardt <dick.hardt@gmail.com> Tue, 17 July 2018 16:17 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 ECCC1130F2C for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2018 09:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_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 a6e9awp_m0TM for <oauth@ietfa.amsl.com>; Tue, 17 Jul 2018 09:17:09 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 0FB88130E7F for <oauth@ietf.org>; Tue, 17 Jul 2018 09:17:09 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id e6-v6so659896pgv.2 for <oauth@ietf.org>; Tue, 17 Jul 2018 09:17:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UNB18PmKjlRcWmRxYDj/iej+4WcYtuevuGFU8nneBTY=; b=F2ow6a/Qf+yKfvgne9FcogOaZuSvsOQVVB1O4xZQttk4zlvWA36dz437VNs3DEhp8L vVqQGh1jqIy9uyRZsSJ07JlIY2nSNE1O6jyDx9d7GPlRQhKe0rmddJp7lMlUB7tcxGdT HnZwB25AK99tKH3iEuvQTA/yHqyTDgsIhYXPkUyiZkY/h59Pu+XwodIUgsxUbw95zrmp v2xk/p3zOBB67+Qze4Dc2qEoMsvloP0I2gsdrh5cSxIYTGnxMp5GDxErIdzHZ8/pX/Q7 Wi/igNmtlYIRxsb/6qNykrj/pTqYLKZpxYv9BT3QQ9L0ZWJZn/ClpJN9p3ReYWz7k0c5 4E6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UNB18PmKjlRcWmRxYDj/iej+4WcYtuevuGFU8nneBTY=; b=iCRNChM9vvH4Y7nioCt6GXOtxIRTS+rnpOUS7jB+hwjYNyYyoLBRSJOluWHQzMKGAx I5+bQ+SjourFbxH0qLLjdvLNGwetXlQTfgqtQdxzn494Xptase8jM6iGENaUCnNJoTgV cXjHGgAj44G0+H/7WDEvapr1K4lnx9DuYS6bS7lzE1hkhG7KPVVo6ZOCU1FWhG/Mry1H licix+JGJ9+82EMQW+s6jSL3JgkPpwLQKV6HV7w7sfL2Y899fn4DWJNCQ7dRX3cNB5+P lWWIqTdnZaYw/CGXlrxV7nbHWWRZ0z3bQNtANKS+4ww9YSlNPn2GEr/Lo3SVTFBb7mfQ UgrQ==
X-Gm-Message-State: AOUpUlFEeMOzyVF6kt/Ql9u36L2iaxqHn+QwEqeLg8nHrgWmk/qXkpzx WHJem4Hoijc7/O4kOZqEThMz5VbLcBTL2wb0Bco=
X-Google-Smtp-Source: AAOMgpeVHFdGbrKvrBwoPDKoGb2mvwV4rjgpIaVGpJMNUz+om3A/KVZT+bEzmTLKt02PmDr8B4OtLKc3xVDNVM9J9nM=
X-Received: by 2002:a63:6243:: with SMTP id w64-v6mr2204033pgb.179.1531844228400; Tue, 17 Jul 2018 09:17:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:9ce:0:0:0:0 with HTTP; Tue, 17 Jul 2018 09:16:47 -0700 (PDT)
In-Reply-To: <B976F6E6-95E3-4B50-A54B-C207FA4D82A7@lodderstedt.net>
References: <CAD9ie-sW7EbfuJWc8_fkLO0wGg9kd0VR=xuO346yOoMK8ZGiyQ@mail.gmail.com> <B976F6E6-95E3-4B50-A54B-C207FA4D82A7@lodderstedt.net>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Tue, 17 Jul 2018 12:16:47 -0400
Message-ID: <CAD9ie-sUM3jQm8pN1e4wUpSAJw=DW=xDXJS--R6icpjJsnV_AA@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000015cbab0571344714"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/DODSkjKa4rgf19Mf4J_NRCv-wEg>
Subject: Re: [OAUTH-WG] updated Distributed OAuth ID
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.27
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, 17 Jul 2018 16:17:24 -0000

Thanks for the review Torsten! ... comments inserted ...

On Tue, Jul 17, 2018 at 11:59 AM, Torsten Lodderstedt <
torsten@lodderstedt.net> wrote:

> Hi Dick,
>
> I like the draft! It puts together some best practices relevant for
> dynamic OAuth in a reasonable way.
>
> Some comments:
>
> Section 2:
> I appreciate the idea to let the resource determine its resource URI
> (later used as aud of the access token). This will allow the RS to segment
> and group its resources as needed.
>

:)


>
> Section 3:
> Don’t you think it could be a useful information to have the resource URI
> available in the authorization flow?I would assume it could have some
> additional meaning to the AS and could also be the context of the scope.
>

I'm assuming you are referring to the Authorization Code Grant. Good call
out that the resource URI would be useful in the redirect.

The use cases that I have been working with have all been Client Credential
Grants

I currently don't know of a real world use case for the Authorization Code
Grant for Distributed OAuth.


>
> Section 4:
> I think the client MUST authenticate using a PoP (asymmetric crypto based)
> mechanisms due to the attack angle given in 6.3
> Did you intentionally restricted the draft to single resources?


yes


> I would desire support for an integrated UI flow for authorizing access to
> multiple resources at once. This makes sense in multi-service deployments.
>

It could be. Would be great to get some real use cases for that in an
Authorization Code Grant.


>
> Section 6.1.
> I suggest you also refer to https://tools.ietf.org/html/
> draft-ietf-oauth-security-topics-06#section-3.7 for a comprehensive
> discussion of this threat.
>

Thanks


>
> kind regards,
> Torsten.
>
>
> > Am 12.06.2018 um 21:28 schrieb Dick Hardt <dick.hardt@gmail.com>om>:
> >
> > Hey OAuth WG
> >
> > I have worked with Nat and Brian to merge our concepts and those are
> captured in the updated draft.
> >
> > https://datatracker.ietf.org/doc/draft-hardt-oauth-distributed/
> >
> > We are hopeful the WG will adopt this draft as a WG document.
> >
> > Any comments and feedback are welcome!
> >
> > /Dick
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
>
>