Re: [OAUTH-WG] draft-bertocci-oauth-access-token-jwt-00

Hans Zandbelt <hans.zandbelt@zmartzone.eu> Mon, 06 May 2019 20:48 UTC

Return-Path: <hans.zandbelt@zmartzone.eu>
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 F3B42120073 for <oauth@ietfa.amsl.com>; Mon, 6 May 2019 13:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=zmartzone-eu.20150623.gappssmtp.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 Voe_0lxSBa_c for <oauth@ietfa.amsl.com>; Mon, 6 May 2019 13:48:49 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 BBAC01201E3 for <oauth@ietf.org>; Mon, 6 May 2019 13:48:48 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id f24so6098420qtk.11 for <oauth@ietf.org>; Mon, 06 May 2019 13:48:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zmartzone-eu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0hEFR11CgLChPFOz5KfNNKut7pgSr48ZLnR4YgrJ8HI=; b=aqTE/8wy1VGpPYCJSmViXssq4AmbmGF1lo2xzydzjpfSYBMBSaU9s6d/dnTEg7U6MO wVGDh8buEY2m6fN4n+ZmlEvV7+/W6fnfuHbL/txX/0ZyOmY2YHTtqYTclY3JWmtuRS4q wG3Z3Lxe5LkqjffWJGcjKUd/sX9FU5rX8I8hUOgERLw5VchaS4yJ4/4dwLXKp4zVrrIi x/mp8HNzhUdFjAnu9OIqihD6Pziiza3Lrvi2l1DqsyqX9pBl8RczIYTNq1dtZTJw2mGN UsE1mxZCSj1q10tMfrW9KcnFpktPvPGBLZShYhFl6UufB9u2Lg1iDcpDv201eJhUXXAC XZsQ==
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=0hEFR11CgLChPFOz5KfNNKut7pgSr48ZLnR4YgrJ8HI=; b=jAykuRdpJQLH6giKSIQigo7G/veoKQ1X8gIpK5//PASCiT7nXHFt9eydvtlBkAqRVJ pYqO2ZSwyk+ZM0o8+l3L7/8+0bth82LTn2tLShTMNDaXZ+LPw8eWHEHiqVii4YcSnFHl AMo469+zvNYpU4VChta0NDQEwHWLS60p/xScBgNbVd/2lvIuIGW6eTy8dgjk+QFsqMf6 jNTMtL2Y/s7OQ0Uzolv6oFfvPiVAHAKmu3MFVhyfEw/FG/nNKpeC1ckbZoxrhPRomThu /ZKOGyOKG4Bvuij/JevHrsmJ3ydDeA0VtSDn8dpHtoffNwOYuEujcAtradZfEqqTquFq pVFg==
X-Gm-Message-State: APjAAAVBTq2MbdK0Kzx+PJP8v0IweF8bkuj5rsc8FCe4FOh/fP1Z/XOD bVybId9BJ0cgav6Aw29hfFmPZZMT41PjiOBQlRv5Xg==
X-Google-Smtp-Source: APXvYqxaJ89otnkglgknckpitJRAvUXOAzH3f9LnqU3NubfQW9wRTTPpQZlbOQSubzfx/88qd184SFTIwoX2RGb0NJk=
X-Received: by 2002:ac8:1bec:: with SMTP id m41mr21737519qtk.272.1557175727835; Mon, 06 May 2019 13:48:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAO_FVe6eWy3zppQAij7qxD+ycYL8ebqGJKG0y-A7GhN+0=kb4g@mail.gmail.com> <CAHsNOKewL9xCFt6SsP4dz+W0CN_NUZaGMJahF7mSgos_Xbnhhw@mail.gmail.com> <CAO_FVe7c6jLRJ8mD7gw=a6NY3oZcgCh_b5dR8uRXa6Q2c2gmGg@mail.gmail.com> <CA+iA6uje229zrAos3c1TCuJEM+2vmVifNQ2FnKDuj2T4ET2SYA@mail.gmail.com> <a34edf0e-012a-ecc9-e547-3cdc61dca5a4@aol.com> <CA+iA6uh6Q901wEaqGSK7An0z0_iJTjCfvPVN44Qwpb=M_rDONg@mail.gmail.com> <239f40ab-da4d-03fe-4524-0b21a0bcc63e@aol.com> <SN6PR00MB0304BC3C7D438F8A5715B36DF5500@SN6PR00MB0304.namprd00.prod.outlook.com> <CA+iA6ugr+xPfeTFXK2gGBFX8Yw+zGArGfav=Ci5A3qNYUqB7rw@mail.gmail.com> <SN6PR00MB030459810B40D98370728BBAF5500@SN6PR00MB0304.namprd00.prod.outlook.com> <CA+iA6ug1NOpMcPsSr8o24CM3xWy-3z_pxiZhiyPeKxvScMACmg@mail.gmail.com> <CAO_FVe4AP5aWgXAAGj1QxPDFPjyfeaZGWd-b5azrz=ajuHuJdQ@mail.gmail.com> <3ec04cf7-e0ed-2b9a-20f7-a94dea4d559b@connect2id.com> <CAO_FVe6sLxbkk0tEjH5sb8k36q4_sJLU6HAgU05fAqOGaqo8MA@mail.gmail.com> <61adde0e-8709-5b88-8b64-ac8cc4549f51@connect2id.com> <CAO_FVe4HQKPvL5bdbAerHRU0TCiZKLJS9JgDrYkXNokri9oBaA@mail.gmail.com> <2C153797-C5AD-410D-A52E-B87DBA19DF99@okta.com>
In-Reply-To: <2C153797-C5AD-410D-A52E-B87DBA19DF99@okta.com>
From: Hans Zandbelt <hans.zandbelt@zmartzone.eu>
Date: Mon, 06 May 2019 21:48:36 +0100
Message-ID: <CA+iA6uig=Pud6h8T=n9rY7vvkc97=80K-0JQOXhgv2mQBt3kPQ@mail.gmail.com>
To: Karl McGuinness <kmcguinness=40okta.com@dmarc.ietf.org>
Cc: Vittorio Bertocci <Vittorio=40auth0.com@dmarc.ietf.org>, IETF oauth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001c623905883e3a5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/buYfPQ_Xd6KSnIGZ7IKo7UcydMA>
Subject: Re: [OAUTH-WG] draft-bertocci-oauth-access-token-jwt-00
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: Mon, 06 May 2019 20:48:52 -0000

I may be missing something but I'd argue that by requiring and comparing
both "sub" and "client_id" we achieve the same semantics without a
new/additional claim (barring name spacing)

Hans.

On Mon, May 6, 2019 at 8:58 PM Karl McGuinness <kmcguinness=
40okta.com@dmarc.ietf.org> wrote:

> Makes sense that we don’t want to further couple AS and RS with grant
> types.  I’m OK if we want a dedicated claim to establish whether the token
> is resource owner delegated  vs client acting as itself.
>
> Subject Type is already a concept in RISC.  Just making folks are aware of
> prior art.
>
> https://openid.net/specs/oauth-event-types-1_0-01.html#rfc.section.2.2
> https://openid.net/specs/openid-risc-profile-1_0.html#rfc.section.2.1
>
> -Karl
>
> On May 6, 2019, at 12:42 PM, Vittorio Bertocci <
> Vittorio=40auth0.com@dmarc.ietf.org> wrote:
>
> *This message originated outside your organization.*
> ------------------------------
> Fair enough! What others think about it?
> Exploring the approach: would we want a bool claim or an enumeration, e.g.
> sub_type = [ resource_owner | client ] ?
>
>
> On Mon, May 6, 2019 at 12:35 PM Vladimir Dzhuvinov <
> vladimir@connect2id.com> wrote:
>
>> Hi Vittorio,
>>
>> On 06/05/2019 22:22, Vittorio Bertocci wrote:
>> > It is true that the grant_type is a client side consideration. I did
>> think
>> > about the "client_id==sub" heuristic, but that's not always applicable:
>> > many systems have their own rules for generating sub, and in case they
>> want
>> > to prevent tracking across RSes the sub might be generated ad-hoc for
>> that
>> > particular RS.
>> > Would you prefer to have a dedicated claim that distinguish between user
>> > and app tokens rather than reusing grant_type?
>>
>> A dedicated claim to flag client_id effectively == sub would be
>> preferable, and much easier for RS developers to process.
>>
>> The AS is the authority and has all the knowledge to set / indicate this.
>>
>> I want to keep RS developers away from having to deal with grant types
>> and having to make decisions whether client_id effectively == sub.
>>
>> Vladimir
>>
>>
>> > On Mon, May 6, 2019 at 12:16 PM Vladimir Dzhuvinov <
>> vladimir@connect2id.com>
>> > wrote:
>> >
>> >> On 06/05/2019 20:32, Vittorio Bertocci wrote:
>> >>> To that end, *Karl MCGuinness suggested that we include
>> >>> grant_type as a return claim, which the RS could use to the same
>> >> effect*. I
>> >>> find the proposal very clever, and the people at IIW thought so as
>> well.
>> >>> What you think?
>> >> The grant type is not something that the RS is really concerned with,
>> or
>> >> should be. Introducing this parameter in the access token will create
>> an
>> >> additional logical dependency, plus complexity - in the system of
>> >> client, AS and RS as a whole, as well as for RS developers. The grant
>> >> type, as a concept, is a matter between the client and AS, and IMO
>> >> should stay that way.
>> >>
>> >> Clear language in the spec should suffice. For instance: "If the sub
>> >> value matches the client_id value, then the subject is the client
>> >> application".
>> >>
>> >> Vladimir
>> >>
>> >> --
>> >> Vladimir Dzhuvinov
>> >>
>> >>
>> >> _______________________________________________
>> >> OAuth mailing list
>> >> OAuth@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/oauth
>> >>
>> --
>> Vladimir Dzhuvinov
>>
>>
>> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>


-- 
hans.zandbelt@zmartzone.eu
ZmartZone IAM - www.zmartzone.eu