Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Discovery

Torsten Lodderstedt <torsten@lodderstedt.net> Sat, 06 February 2016 11:15 UTC

Return-Path: <torsten@lodderstedt.net>
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 85C0A1B2BC2 for <oauth@ietfa.amsl.com>; Sat, 6 Feb 2016 03:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.049
X-Spam-Level:
X-Spam-Status: No, score=0.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MANGLED_PREMTR=2.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 Gbe4hhz9lVd5 for <oauth@ietfa.amsl.com>; Sat, 6 Feb 2016 03:15:19 -0800 (PST)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA1141B2BBC for <oauth@ietf.org>; Sat, 6 Feb 2016 03:15:18 -0800 (PST)
Received: from [79.218.87.147] (helo=[192.168.71.102]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <torsten@lodderstedt.net>) id 1aS0pf-00026n-Vz; Sat, 06 Feb 2016 12:15:16 +0100
To: Justin Richer <jricher@mit.edu>, Roland Hedberg <roland.hedberg@umu.se>
References: <569E2298.3010508@gmx.net> <BY2PR03MB44237A6E59B1E76D9B7D14CF5D10@BY2PR03MB442.namprd03.prod.outlook.com> <CAAP42hATYHF1meMjJ_Exu=G5d-xWXcky2nNwny1DwWqxf3ZE6Q@mail.gmail.com> <0B9E9D6E-67A9-4956-BFA2-9A90CD39087A@oracle.com> <E04315CD-4FD3-4B06-BD33-22FF6DC5EB38@adm.umu.se> <2DE2E1FE-BBB0-489B-9479-888A7D36E6C8@mit.edu>
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Message-ID: <56B5D5AB.9070801@lodderstedt.net>
Date: Sat, 6 Feb 2016 12:14:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2DE2E1FE-BBB0-489B-9479-888A7D36E6C8@mit.edu>
Content-Type: multipart/alternative; boundary="------------090400090400020800010208"
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQ=
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/aT3gNz5fjWjCposvoMdEZKrWNTQ>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Discovery
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: Sat, 06 Feb 2016 11:15:22 -0000

I think the service discovery document (describing all the endpoints and 
features of the AS) is a valid starting point. That's basically how we 
use the OIDC discovery in the OAuth context today at DT. We refer 
partners to the openid-configuration document. Putting the data relevant 
to OAuth under .well_known/oauth would be more reasonable from a OAuth 
developer's perspective (in my opinion).

We still have to learn, how clients really discover the location of this 
discovery document. We can come up with extensions for user id/resource 
service data based discovery at any time, if we

kind regards,
Torsten.

Am 05.02.2016 um 01:34 schrieb Justin Richer:
> +1, if we define a webfinger/rel at all.
>
> I would rather we just define the service discovery document, the thing that lives under .well-known.
>
>   — Justin
>
>
>> On Feb 4, 2016, at 4:01 AM, Roland Hedberg <roland.hedberg@umu.se> wrote:
>>
>> +1
>>
>>> 4 feb 2016 kl. 08:10 skrev Phil Hunt <phil.hunt@oracle.com>om>:
>>>
>>> +1 for adoption.
>>>
>>> However I would like a rel value distinct from OpenID (see separate email). While the mechanics of discovery is the same, I believe some clients will want to distinguish between OAuth AS’s and OIDC OPs.  Further, I would expect over time that different discovery features may be required. Locking them together seems like a pre-mature or rush choice.
>>>
>>> Phil
>>>
>>> @independentid
>>> www.independentid.com
>>> phil.hunt@oracle.com
>>>
>>>
>>>
>>>
>>>
>>>> On Feb 3, 2016, at 10:44 PM, William Denniss <wdenniss@google.com> wrote:
>>>>
>>>> +1 for adoption of this document by the working group
>>>>
>>>> On Wed, Feb 3, 2016 at 10:27 PM, Mike Jones <Michael.Jones@microsoft.com> wrote:
>>>> I support adoption of this document by the working group.  I'll note that elements of this specification are already in production use by multiple parties.
>>>>
>>>>                                 -- Mike
>>>>
>>>> -----Original Message-----
>>>> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Hannes Tschofenig
>>>> Sent: Tuesday, January 19, 2016 3:49 AM
>>>> To: oauth@ietf.org
>>>> Subject: [OAUTH-WG] Call for Adoption: OAuth 2.0 Discovery
>>>>
>>>> Hi all,
>>>>
>>>> this is the call for adoption of OAuth 2.0 Discovery, see
>>>> https://tools.ietf.org/html/draft-jones-oauth-discovery-00
>>>>
>>>> Please let us know by Feb 2nd whether you accept / object to the adoption of this document as a starting point for work in the OAuth working group.
>>>>
>>>> Note: If you already stated your opinion at the IETF meeting in Yokohama then you don't need to re-state your opinion, if you want.
>>>>
>>>> The feedback at the Yokohama IETF meeting was the following: 19 for / zero against / 4 persons need more information.
>>>>
>>>> Ciao
>>>> Hannes & Derek
>>>>
>>>> _______________________________________________
>>>> 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 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 list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth