Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
Nat Sakimura <sakimura@gmail.com> Wed, 20 January 2016 23:48 UTC
Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00B991B2AEA for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 15:48:10 -0800 (PST)
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, SPF_PASS=-0.001] autolearn=ham
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 AEqa99ytV_MI for <oauth@ietfa.amsl.com>; Wed, 20 Jan 2016 15:48:08 -0800 (PST)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (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 F2B771B2AE6 for <oauth@ietf.org>; Wed, 20 Jan 2016 15:48:07 -0800 (PST)
Received: by mail-qk0-x234.google.com with SMTP id s68so9822930qkh.3 for <oauth@ietf.org>; Wed, 20 Jan 2016 15:48:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=16dJ4tHrPnAhUliOZzVsAnlERdER1A4z/O9THqUjxKU=; b=JplJy4qSpCoF56mVR93BO23SdBQz9uDxPjhDLWgWhAZ5bOlXYOrj2NNiFOb7bZgisP f2RMiggZ4Dy+qSEq+Zy6ViS5A1QJMbG8XRGYAT+K55DQXEFJIhrrlup0Ezd4ZALtR4/m apxXh6Ddn59cJkEjWGidgGYgLyn/JtdKF31ikMiBV7YEEk22A+bq+EUnp26LGnAZMW3Q mc3OsYo/Y3kfTRG0DgkIcfT3ZdJpQe5IOxl7XFUkOafC/k5/ddMwumYl9pDYAGrB0u5+ 1nOzushiVG2UFd/NXIIU8WmCIobm5uXareCCKveGukSI60D+NihRx6gQSpGftPk4vLML UYiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=16dJ4tHrPnAhUliOZzVsAnlERdER1A4z/O9THqUjxKU=; b=d/In374ToK2wAWcRV7vsYEIQx6fP/HHpwV7N1PQlYhhDeGaq8micBeHQvh0o32KY/U 88ZKIEox9X6ycZ7xWj08aiG7dgQXrcHKmTxNxL3K7G915+Wj3m64djgwjXX9g7bnwtNp VZ8L5XbGVgWSSGkud34eOyy0Lbt/mx+xhgKM9EkrkRCXIdM7FPqMnWWXZj0xfQfMHVo4 kwEL37Pt5HKLBhRG7KFL8XSVf5IY0LYXfOx5xdcIH5DR6hD3mcQoKVHPpbwL0vI7X+n2 3A+2/4AW1D/RB64DgFl01BZjh7cYLykHZfKlKDEYCUn6UBcrojZjddKv2E66aVbXnDvz ENjQ==
X-Gm-Message-State: ALoCoQmLLSNXZ/vS2VWTpztiYKRiA9mNHS29gduO1IsGF67AbhQYhsRVxutOF4coQCVNdHLoZowHeZUK2W6Kv+teJ6zzNHmrSQ==
X-Received: by 10.55.15.139 with SMTP id 11mr48214666qkp.50.1453333687184; Wed, 20 Jan 2016 15:48:07 -0800 (PST)
MIME-Version: 1.0
References: <568D24DD.3050501@connect2id.com> <EA392E73-1C01-42DC-B21D-09F570239D5E@ve7jtb.com> <CAAP42hAA6SOvfxjfuQdjoPfSh3HmK=a7PCQ_sPXTmDg+AQ6sug@mail.gmail.com> <568D5610.6000506@lodderstedt.net> <CAAP42hA8SyOOkJ-D299VgvQUdQv6NXqxSt9R0TK7Zk7JaU56eQ@mail.gmail.com>
In-Reply-To: <CAAP42hA8SyOOkJ-D299VgvQUdQv6NXqxSt9R0TK7Zk7JaU56eQ@mail.gmail.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Wed, 20 Jan 2016 23:47:56 +0000
Message-ID: <CABzCy2COm57O6T=6ayfhV5QzNy6L=Qq2F0geX+P0A48=RR7-oQ@mail.gmail.com>
To: William Denniss <wdenniss@google.com>, Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: multipart/alternative; boundary="001a1147446e2a33f40529cc9ef5"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/bgy51nB0cbmOSUS6JUmYtz41mzc>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Discovery (draft-jones-oauth-discovery-00)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 20 Jan 2016 23:48:10 -0000
I kind of prefer pkce_methods_supported as it scopes it more narrowly and less likely to be overloaded. 2016年1月19日(火) 11:59 William Denniss <wdenniss@google.com>: > Seems like we agree this should be added. How should it look? > > Two ideas: > > "code_challenge_methods_supported": ["plain", "S256"] > > or > > "pkce_methods_supported": ["plain", "S256"] > > > > On Wed, Jan 6, 2016 at 9:59 AM, Torsten Lodderstedt < > torsten@lodderstedt.net> wrote: > >> +1 >> >> >> Am 06.01.2016 um 18:25 schrieb William Denniss: >> >> +1 >> >> On Wed, Jan 6, 2016 at 6:40 AM, John Bradley <ve7jtb@ve7jtb.com> wrote: >> >>> Good point. Now that PKCE is a RFC we should add it to discovery. >>> >>> John B. >>> > On Jan 6, 2016, at 9:29 AM, Vladimir Dzhuvinov < >>> vladimir@connect2id.com> wrote: >>> > >>> > I just noticed PKCE support is missing from the discovery metadata. >>> > >>> > Is it a good idea to add it? >>> > >>> > Cheers, >>> > >>> > Vladimir >>> > >>> > -- >>> > 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 >>> >> >> >> >> _______________________________________________ >> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth >> >> >> > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] Advertise PKCE support in OAuth 2.0 Di… Vladimir Dzhuvinov
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Torsten Lodderstedt
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… nov matake
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Nat Sakimura
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Phil Hunt
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… John Bradley
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Mike Jones
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… William Denniss
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Mike Jones
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Dominick Baier
- Re: [OAUTH-WG] Advertise PKCE support in OAuth 2.… Dominick Baier