Re: [OAUTH-WG] OAuth 2.0 Discovery Location

Thomas Broyer <> Mon, 22 February 2016 09:44 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3D3631B2F0E for <>; Mon, 22 Feb 2016 01:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lveDpsNpZKdz for <>; Mon, 22 Feb 2016 01:44:28 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D5C9C1B2EEB for <>; Mon, 22 Feb 2016 01:44:27 -0800 (PST)
Received: by with SMTP id of3so78596762lbc.1 for <>; Mon, 22 Feb 2016 01:44:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-type; bh=FDOAyR9pj8XVGr4Eh+E4x/hoJlOzVi7VjWJC52g6SXo=; b=BPHxaUDdNWo+hAeE/VmPwjOPC3ZLaxmAmzyEl7AC09EUuTEM9Lmxn2x753V0WAL+AB hzV78cT3tKTsFBXs/HF1pZnqgPGHpezNhc1fkZw270YFX8e1c/tbZUlKOgHkSeRis8+d Tj1ByAJSDRW1Nz8CbZzcCmeRa9mcTnCpwMLGgpbWTLIocUDqC17rKDZh4AavaeYiZGMr 6Pz8Mqtsh62NgdaIyuNO5l9o/0+YVtFEAwsLhLb1cRyUwY6VgNdUmPYO1uPlHwbW/wN8 PCbQmkvQHlxktiiuOCiyVxh515kJRFhLXnk1khWHhpcz8mAwHub5d3b9uZhLHbiVGLiD 0O3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=FDOAyR9pj8XVGr4Eh+E4x/hoJlOzVi7VjWJC52g6SXo=; b=O/RyjZGxbkKPIh/IVtcYJdIJYauR0hfhYSqLT/cDa44fFuOZHY59EESIllO0JGkkWs rulXnYWRPpU1QSgqtOtFMOhuGR3UfGy2SY8J5G28UMRecPT+GuCcASMzQMsNKDur4+n0 OwD2i0XReng/3+05jOlZgJ2Q6Yi2XoqZqOknHdS8/qM85dOrpKDDdszCzMskF+Y2Vi9/ EdPFwV+7QtORMnHz2/EP27w3AAEXMn/F45PHzzFPXdBIHuO/0bkoGTGyvLS6yAd/N4lv 6dUf6mxLtQYQTfMqNdltBYAhlotZILlQyo2PHYjDgTrWzIuGW9vzaECs9CnZEAJu56TO W4tA==
X-Gm-Message-State: AG10YOTXOFq/SFy80SFyB2JM3phqw6e9Gx2FErXbvTggplUx6b3Vxzl4jaWfa2T3HYx/g9kcByd5iVStrTkzPQ==
X-Received: by with SMTP id i2mr9589611lbj.107.1456134266152; Mon, 22 Feb 2016 01:44:26 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Thomas Broyer <>
Date: Mon, 22 Feb 2016 09:44:16 +0000
Message-ID: <>
To: Justin Richer <>, "<>" <>
Content-Type: multipart/alternative; boundary="001a11c36b66adf063052c58adac"
Archived-At: <>
Subject: Re: [OAUTH-WG] OAuth 2.0 Discovery Location
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 22 Feb 2016 09:44:30 -0000

Couldn't the document only describe the metadata?
I quite like the idea of draft-sakimura-oauth-meta if you really want to do
discovery, and leave it open to implementers / to other specs to define a
.well-known URL for "auto-configuration".
The metadata described here would then either be used as-is, at any URL,
returned as draft-sakimura-oauth-meta metadata at the RS; or as a basis for
other metadata specs (like OpenID Connect).
With draft-sakimura-oauth-meta's "duri" and the "scope" attribute of
WWW-Authenticate response header, you have everything you need to proceed
(well, except if there are several ASs each with different scopes; sounds
like an edge-case to me though; maybe RFC6750 should instead be updated
with such a parameter such that an RS could return several
WWW-Authenticate: Bearer, each with its own "scope" and "duri" value?)

On Fri, Feb 19, 2016 at 10:59 PM Justin Richer <> wrote:

> The newly-trimmed OAuth Discovery document is helpful and moving in the
> right direction. It does, however, still have too many vestiges of its
> OpenID Connect origins. One issue in particular still really bothers me:
> the use of “/.well-known/openid-configuration” in the discovery portion. Is
> this an OAuth discovery document, or an OpenID Connect one? There is
> absolutely no compelling reason to tie the URL to the OIDC discovery
> mechanism.
> I propose that we use “/.well-known/oauth-authorization-server” as the
> default discovery location, and state that the document MAY also be
> reachable from “/.well-known/openid-configuration” if the server also
> provides OpenID Connect on the same domain. Other applications SHOULD use
> the same parameter names to describe OAuth endpoints and functions inside
> their service-specific discovery document.
>  — Justin
> _______________________________________________
> OAuth mailing list