[OAUTH-WG] ID Token by Device Flow
Takahiko Kawasaki <taka@authlete.com> Thu, 20 June 2019 22:33 UTC
Return-Path: <taka@authlete.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 BEF0C120183 for <oauth@ietfa.amsl.com>; Thu, 20 Jun 2019 15:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=authlete-com.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 CcrPTUdhqp5Q for <oauth@ietfa.amsl.com>; Thu, 20 Jun 2019 15:33:04 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 905691200D8 for <oauth@ietf.org>; Thu, 20 Jun 2019 15:33:04 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id d4so6882957edr.13 for <oauth@ietf.org>; Thu, 20 Jun 2019 15:33:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=authlete-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=r0Qh19kjLwbOhLasCEZEwiEtDMMidhcTmz8p9WEsbkY=; b=zq0Luyl/+962ViPF+di4Da4LenzrtUVuy+sR7/UhodipulaUxw0Mn4R793sT+QZrOY uGDEGQwLJ+Rj7E3loI1+L1sMKOi0HNNDgh4v62sQaEF+NxYrZ9O7jF297JN2wX3gm+Fp mHeDnBCgEuTWfAbsnpwNTbcgOVnGuJO5Vk8Klt7h/9SJqA3B0bXNSYMrQ8+4pws8dJ8O 0tmRjhzHlOc9bvYPz0k3LqUOJt0UZ1J/RAkDo7flGw5LO+ZMWVfcDPrln0oKVxlzi2AH k8fTJHb01jLySzAzX+cyMJatrTcByDzjvLlsAnTXO4pK17gy6+MisVRlPX2nzj99MGpO vKPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=r0Qh19kjLwbOhLasCEZEwiEtDMMidhcTmz8p9WEsbkY=; b=WaRuTi3clNyAshcXhnr4/N2RYR3ZKJpOFO/+VOmkJfeSyfF2ymNAhQZA9DAnNHEiDI 2ekWaOKBJCjzuArz3v4TpdtxkWl7/cxTaOiiUThQdC3DzfzL18oprU5CDcoOzV+vc2yl RtEFSKD7AIXXCbYwdUiczoj/BeL3HvsqrVz2qec0ngG0qLxr8UTJxcOdZbh1xZyyAeex LykgWYeiv65J4GQDuVG7HTy2cTWFWhlPDz7WTVW1SGN6L24Jto/FfxRkzh/55gc9rHJn 5iFB7o80+6qruo2KSO28+iN8luexy0dA6JUbO2XnIdZbg0aJAgTGhFC5dtEPkxMvnEup KP/A==
X-Gm-Message-State: APjAAAVr9OVdZxEZ3OQSt2DJ/cgu9a50TPTgPWCv8DJ6fOaxws0h64xl uurbFb14NceRwM6WfVfV3uJdaj0tDzGDe5jAGnIkLX8QjNM=
X-Google-Smtp-Source: APXvYqwLlsDxApyceP80X0YI8RVxCBCYzfgRvRMaQQ12J7xnl8ZvhpuDI3gvLim0x7SwIw/uCjhurn9ZjiV5/MeyUec=
X-Received: by 2002:a50:a544:: with SMTP id z4mr5199387edb.71.1561069982840; Thu, 20 Jun 2019 15:33:02 -0700 (PDT)
MIME-Version: 1.0
From: Takahiko Kawasaki <taka@authlete.com>
Date: Thu, 20 Jun 2019 18:32:51 -0400
Message-ID: <CAHdPCmORS1=nEK9xSP-2hovCfyrt6RK78E1ciJGMYypS7CW+Tw@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cc0d2a058bc8ed03"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/dP_0PS44EpU8DZ-t8CMSq2yTTlw>
Subject: [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: Thu, 20 Jun 2019 22:33:07 -0000
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-WG] ID Token by Device Flow Takahiko Kawasaki
- Re: [OAUTH-WG] ID Token by Device Flow Justin Richer
- Re: [OAUTH-WG] ID Token by Device Flow Takahiko Kawasaki
- Re: [OAUTH-WG] ID Token by Device Flow William Denniss
- Re: [OAUTH-WG] ID Token by Device Flow Nat Sakimura