Re: [OAUTH-WG] ID Token by Device Flow

William Denniss <wdenniss@google.com> Tue, 25 June 2019 00:17 UTC

Return-Path: <wdenniss@google.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 D1C6B12016C for <oauth@ietfa.amsl.com>; Mon, 24 Jun 2019 17:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 JD7BbAMJ-BFE for <oauth@ietfa.amsl.com>; Mon, 24 Jun 2019 17:17:23 -0700 (PDT)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 5121D1200B6 for <oauth@ietf.org>; Mon, 24 Jun 2019 17:17:23 -0700 (PDT)
Received: by mail-ot1-x32c.google.com with SMTP id e8so15399068otl.7 for <oauth@ietf.org>; Mon, 24 Jun 2019 17:17:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5oAZgzq/qFNe19AvEFG59U/enlru6Nr5210d8PLSjPw=; b=sYGwCHfuJw4Tb8fOqJQnCUTjpti3Z75zivCCYb1+0Z8b6Y343EsTljrxdtqAWN/ouh NXzz+23KwM28GB5kEzOaYeMVXWlYYn3wvQyFNWPgUl6wdxH3y3GE6Uxx6CijAsOcUX0T /sVCGXT7dv62B7agTf0gn2A4pVI5iwG+vfJSjXfwVYHUON8CFDRCdpk9dZ7XFnIV8TEX S7MxPGfJ2sMz37AVyEEPu2rQcCOrgP3U74M2c0AAXlRgj/US2DZqHrdJ2N1WxiLhOdz7 u0/v8Lv98OVtvMUuO2fpn8PKVzJh6mmdgW/Dib6ilaEnDh2e3e96uXihO7u8Smqpkyi5 k7mw==
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=5oAZgzq/qFNe19AvEFG59U/enlru6Nr5210d8PLSjPw=; b=myQyU3rXQ1oan+V4slVpgemKcdbe9KXl7UoAdk1hp+A4+mfBJcDJWGACTGsw7+uqzb rIAp/bhJaolm8WFxerIVU91LjISh/Br/58IC08NRaarXUVBhP8QcdFp/uj1W3dQK4Zlw aWamtETLIx0GIy3j3JxwVT5/ZBtmdU98UvH7+USLQHqL74EkMJq0hJEQ3Asl1hq/exhz wJIXy9vDFGMGa5XElskuEU0SZBZwFih8Dw+wAltzihCu4kibfMPkv6Sd9D88C/LzaHSv h/2onLprjVW0+3SUOUxTH4qmR1U5zH559bTcKmzY4EmCh0NLwuj4iVs24FcJ0fDnBP3g iW6A==
X-Gm-Message-State: APjAAAXFk54bcF3mwe/NWSJmKF17oBB4UWYMztVFpL8Wh4u7FGLIDo5D +3P4n3i59BFkkHmI3xO3Uajr8CadfsuEpg+duz4eGQ==
X-Google-Smtp-Source: APXvYqxK2oBJfDHAzrhpzX4sy3l8BEL3ypc3ya6qJ7i9qVLeDOHcd71NPDO5sWAxyjHhsbqdL6qWw9+8I3ZFuVNyGxI=
X-Received: by 2002:a05:6830:14c:: with SMTP id j12mr13330238otp.181.1561421842218; Mon, 24 Jun 2019 17:17:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAHdPCmORS1=nEK9xSP-2hovCfyrt6RK78E1ciJGMYypS7CW+Tw@mail.gmail.com> <846314DA-2A9F-41EE-BD21-61EC1CCB80ED@mit.edu> <CAHdPCmO9Uyz_yRA5AbFoy_fpDat4K9P6AZCQZGgH31ZyreS94A@mail.gmail.com>
In-Reply-To: <CAHdPCmO9Uyz_yRA5AbFoy_fpDat4K9P6AZCQZGgH31ZyreS94A@mail.gmail.com>
From: William Denniss <wdenniss@google.com>
Date: Mon, 24 Jun 2019 17:17:13 -0700
Message-ID: <CAAP42hBceAvbbg0DS+V4Y1hq_76Wn4faVA2WWf7LVcLNuVQQ=A@mail.gmail.com>
To: Takahiko Kawasaki <taka@authlete.com>
Cc: Justin Richer <jricher@mit.edu>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004067d0058c1adac0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/3p_6bXF_EsdEbroxxtnnhbPCKqk>
Subject: Re: [OAUTH-WG] ID Token by Device Flow
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, 25 Jun 2019 00:17:27 -0000

Hi Taka,

On Mon, Jun 24, 2019 at 12:16 PM Takahiko Kawasaki <taka@authlete.com>
wrote:

> Hi Justin,
>
> Thank you. Consensus will be that "openid" in the "scope" request
> parameter should trigger generation of an ID token.
>

+1, and the last time I checked, that’s how Google's implementation
behaved.

I'm wondering if the WG plans to mention it explicitly in the spec and add
> "acr_values" request parameter.
>

No plans to do this. The spec is in the edit queue so such a change can't
be made and as Justin said it may be more appropriate in OpenID Foundation,
if it's needed.

Best,
William


> Best Regards,
> Taka
>
>
> 2019年6月25日(火) 1:13 Justin Richer <jricher@mit.edu>:
>
>> Taka,
>>
>> My reading is that the device flow, like other OAuth flows, does not
>> prohibit extension, including passing back identity assertions like the ID
>> Token. Since it inherits the token response from core OAuth 2, the ID Token
>> could be issued along side the access token just like in the authorization
>> code flow.The user is present and interacting at the AS in both cases. In
>> fact, I’d say that there are enough similarities between the two that for
>> the most part it should “just work” and fit the assumptions of most
>> clients. That said, it’s technically true that there is no defined profile
>> for the combination of the device flow and OIDC, but if something like that
>> were to be written it would be better fit to the OpenID Foundation.
>>
>> — Justin
>>
>> On Jun 20, 2019, at 6:32 PM, Takahiko Kawasaki <taka@authlete.com> wrote:
>>
>> Hello,
>>
>> Do you have any plan to update the specification of Device Flow to
>> support issue of ID tokens?
>>
>> OAuth 2.0 Device Authorization Grant
>>
>> https://datatracker.ietf.org/doc/draft-ietf-oauth-device-flow/?include_text=1
>>
>> Best Regards,
>> Takahiko Kawasaki
>>
>> _______________________________________________
>> 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
>