Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Discovery
Torsten Lodderstedt <torsten@lodderstedt.net> Tue, 26 January 2016 19:35 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 719111B2BFF for <oauth@ietfa.amsl.com>; Tue, 26 Jan 2016 11:35:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level:
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 p3J9hs1YDcRQ for <oauth@ietfa.amsl.com>; Tue, 26 Jan 2016 11:35:40 -0800 (PST)
Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.96]) (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 6A9DE1B2BFA for <oauth@ietf.org>; Tue, 26 Jan 2016 11:35:40 -0800 (PST)
Received: from [79.218.87.147] (helo=[192.168.71.102]) by smtprelay06.ispgateway.de with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <torsten@lodderstedt.net>) id 1aO9OL-0000eM-Va; Tue, 26 Jan 2016 20:35:06 +0100
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, "oauth@ietf.org" <oauth@ietf.org>
References: <569E2298.3010508@gmx.net>
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Message-ID: <56A7CA7D.3050602@lodderstedt.net>
Date: Tue, 26 Jan 2016 20:35:25 +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: <569E2298.3010508@gmx.net>
Content-Type: multipart/alternative; boundary="------------030006050304080801010800"
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC5uZXQ=
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/QEdN1gIjlTpG7MJ0NYlWFCdAM0w>
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: Tue, 26 Jan 2016 19:35:43 -0000
Hi, I support the adoption of this document as starting point for our work towards OAuth discovery. Restating what I already posted after the last IETF meeting: It seems the document assumes the AS can always be discoverd using the user id of the resource owner. I think the underlying assumption is resource servers accept access token of different (any?) user specific AS (and OP)? From my perspective, RSs nowadays typically trust _the_ AS of their security domain/ecosystem and all resource owners need to have an user account with this particular AS. So I would assume the process to start at the RS. I think the spec needs to cover the latter case as well. kinds regards, Torsten. Am 19.01.2016 um 12:48 schrieb Hannes Tschofenig: > 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
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Torsten Lodderstedt
- [OAUTH-WG] Call for Adoption: OAuth 2.0 Discovery Hannes Tschofenig
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Torsten Lodderstedt
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Brian Campbell
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Phil Hunt
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… William Denniss
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Mike Jones
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… William Denniss
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Phil Hunt
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Roland Hedberg
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Roland Hedberg
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Justin Richer
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… Phil Hunt
- Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Disco… John Bradley