Re: [OAUTH-WG] OAuth Discovery metadata values added for revocation, introspection, and PKCE

Nat Sakimura <sakimura@gmail.com> Fri, 29 January 2016 13:16 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 B747D1ACC7F for <oauth@ietfa.amsl.com>; Fri, 29 Jan 2016 05:16:01 -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 m6EgV4UcFCdb for <oauth@ietfa.amsl.com>; Fri, 29 Jan 2016 05:15:58 -0800 (PST)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (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 71DCF1ACC72 for <oauth@ietf.org>; Fri, 29 Jan 2016 05:15:58 -0800 (PST)
Received: by mail-qg0-x22d.google.com with SMTP id o11so64522746qge.2 for <oauth@ietf.org>; Fri, 29 Jan 2016 05:15:58 -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 :content-type; bh=wDq/gdGwdgXHjmtpEu6TV5YN6U6M1NTtcTiBetGXNOs=; b=xh3XD/dAZaVAdWxRtGRrSSFCpEQRSOY347i6fydqyZPWH77kf6H0pzFHtrmsOYtuSm B82enQ/3pC0SWMX4kicLY5E1wplyskXMZw5jlWwdHJIjTqCWJa5LPcwnboXnFLI+DqHn Bq5QzOKqOWpKh0d7+iwUtcVI6KmtfBNaqjyYzkpkfAv3IxHVvIvPZbq1131Y/1DThDZN qFeL6wV023qgYsMkzCjN47fPsOLQZO223PPH7HDZH+w2Q12tyStFnWV0DtT8+6nCK5xR bGWUxkBTJ3c/Zx39mxR92t0EFQwYdjzzxZiT5bhrEnGnmAsHDLWAAiaa4sTkGZ0eG92j m/Mg==
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:content-type; bh=wDq/gdGwdgXHjmtpEu6TV5YN6U6M1NTtcTiBetGXNOs=; b=chK9HRzPmktTncKyEHL6WN7CszybqFbda9y5GKGjvBnGjp+ZzlaLfKQGwuIhsxlWkm pgYkJxvnU4tUvLXu1oiauTAo/hNI4PyhTMAHAWv1W+bwjfFHNCZwxmoEDVjyDPTH+TCs /78VIWYVkqB1jkGDO2Nkjk4j918lL9b3nK46/EPqHe/4TTLMffdmRAtVzu3FmBuLhVv7 bULu+LIJhwOeb77MIM407b8o9lOGCMnJAPpjOsBVIGVahXMoDSlRbDED3STvcCwCC/9Y /i86y4/aDKe9IyUbSj7RI/wKmEjnNGr9yczWfTJU+FihPimc/cQ2LiwfbBhRxmXHhT/r mKhA==
X-Gm-Message-State: AG10YOTHwsvlZPWvrLZe6uPeNiLtAKe7UmPFKg8xuG2f/iEQSeNvvDNyJyZKnRPD8UIZlAv788Gpzk2+mu6sTw==
X-Received: by 10.140.250.138 with SMTP id v132mr11143490qhc.0.1454073357646; Fri, 29 Jan 2016 05:15:57 -0800 (PST)
MIME-Version: 1.0
References: <BY2PR03MB442C39923E8F9D96F5975B0F5DA0@BY2PR03MB442.namprd03.prod.outlook.com> <56AB59CA.5070408@connect2id.com>
In-Reply-To: <56AB59CA.5070408@connect2id.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Fri, 29 Jan 2016 13:15:47 +0000
Message-ID: <CABzCy2Cq5czDXCGP5P5UWjcG8JQTwiS9dci2xLzpefUJVNFf0g@mail.gmail.com>
To: Vladimir Dzhuvinov <vladimir@connect2id.com>, oauth@ietf.org
Content-Type: multipart/alternative; boundary=001a113a99d0f5c44f052a78d52c
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/hj_7d6NESc_pRpMqz3sHzO7EuHc>
Subject: Re: [OAUTH-WG] OAuth Discovery metadata values added for revocation, introspection, and PKCE
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: Fri, 29 Jan 2016 13:16:01 -0000

Good question.

It's probably a good idea to be able to advertise this policy in the
discovery.

Perhaps in the line of

pkce_required or rfc7636_required?
The value should be Boolean.

Nat from iPhone


2016年1月29日(金) 21:23 Vladimir Dzhuvinov <vladimir@connect2id.com>om>:

> Thanks Mike, the updated spec looks good!
>
> I have a question related to PKCE:
>
> The PKCE spec seems to imply that an AS may require public clients to use
> a code challenge:
>
> https://tools.ietf.org/html/rfc7636#section-4.4.1
>
> If an AS has such a policy in place, how is this to be advertised? Or is
> that supposed to the enforced when the client gets registered (there are no
> reg params for that at present)?
>
>
> On 28/01/16 19:27, Mike Jones wrote:
>
> The OAuth Discovery specification has been updated to add metadata values for revocation<http://tools.ietf.org/html/rfc7009> <http://tools.ietf.org/html/rfc7009>, introspection<http://tools.ietf.org/html/rfc7662> <http://tools.ietf.org/html/rfc7662>, and PKCE<http://tools.ietf.org/html/rfc7636> <http://tools.ietf.org/html/rfc7636>.  Changes were:
>
> *       Added "revocation_endpoint_auth_methods_supported" and "revocation_endpoint_auth_signing_alg_values_supported" for the revocation endpoint.
>
> *       Added "introspection_endpoint_auth_methods_supported" and "introspection_endpoint_auth_signing_alg_values_supported" for the introspection endpoint.
>
> *       Added "code_challenge_methods_supported" for PKCE.
>
> The specification is available at:
>
> *       http://tools.ietf.org/html/draft-jones-oauth-discovery-01
>
> An HTML-formatted version is also available at:
>
> *       http://self-issued.info/docs/draft-jones-oauth-discovery-01.html
>
>                                                           -- Mike
>
> P.S.  This note was also published at http://self-issued.info/?p=1531 and as @selfissued<https://twitter.com/selfissued> <https://twitter.com/selfissued>.
>
>
>
>
>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
> --
> Vladimir Dzhuvinov
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>