IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header

"William Mills" <wmills@yahoo-inc.com> Thu, 15 July 2010 17:42 UTC

Return-Path: <wmills@yahoo-inc.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 099693A6A56 for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.89
X-Spam-Level:
X-Spam-Status: No, score=-16.89 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_31=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZH6OrBK7a-f2 for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:42:19 -0700 (PDT)
Received: from mrout1-b.corp.re1.yahoo.com (mrout1-b.corp.re1.yahoo.com [69.147.107.20]) by core3.amsl.com (Postfix) with ESMTP id C8F873A69AA for <oauth@ietf.org>; Thu, 15 Jul 2010 10:42:18 -0700 (PDT)
Received: from SNV-EXPF01.ds.corp.yahoo.com (snv-expf01.ds.corp.yahoo.com [207.126.227.250]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o6FHfotw093208; Thu, 15 Jul 2010 10:41:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:x-mimeole:content-class:mime-version: content-type:subject:date:message-id:in-reply-to:x-ms-has-attach: x-ms-tnef-correlator:thread-topic:thread-index:references:from:to:cc:return-path:x-originalarrivaltime; b=na3JYCdeSyTeAeTVA958ZCXl85ZidB/Ob2x9YVAbjfnYURppraX11IJJbD2o7hu4
Received: from SNV-EXVS08.ds.corp.yahoo.com ([207.126.227.8]) by SNV-EXPF01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 15 Jul 2010 10:41:50 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB2445.0113EB4C"
Date: Thu, 15 Jul 2010 10:41:49 -0700
Message-ID: <012AB2B223CB3F4BB846962876F47217059B6CD3@SNV-EXVS08.ds.corp.yahoo.com>
In-Reply-To: <AANLkTill8k-fUFt-IZLWdZinScj4fSBoI4rAiAf1PrYR@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
Thread-Index: AcskRIld3e5LkrNDRTGz4U/ljUagRAAAFP7Q
References: <AANLkTim6az--AdwmEoew2pz3kEjhc_GyEaiyo_0UhSRr@mail.gmail.com><1279205969.18579.55.camel@localhost.localdomain><AANLkTildz62l2Me26Dlrv5nNmp8Z3P8JD1K-ChcWc5IO@mail.gmail.com> <AANLkTill8k-fUFt-IZLWdZinScj4fSBoI4rAiAf1PrYR@mail.gmail.com>
From: William Mills <wmills@yahoo-inc.com>
To: David Recordon <recordond@gmail.com>, Brian Eaton <beaton@google.com>
X-OriginalArrivalTime: 15 Jul 2010 17:41:50.0305 (UTC) FILETIME=[01484D10:01CB2445]
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 15 Jul 2010 17:42:20 -0000

No, the people who don't like the sharing of the namespace between the 2
still don't like it, and the people that can;t stand teh idea of using
oauth2 for anything still won't move.


________________________________

	From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
Behalf Of David Recordon
	Sent: Thursday, July 15, 2010 10:38 AM
	To: Brian Eaton
	Cc: oauth@ietf.org
	Subject: Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
	
	
	I thought this topic had been beaten to death before. An OAuth
1.0 protected resource request includes a variety of oauth_ parameters
whereas OAuth 2.0 just has oauth_token. 

	--David


	On Thu, Jul 15, 2010 at 10:12 AM, Brian Eaton
<beaton@google.com> wrote:
	

		On Thu, Jul 15, 2010 at 7:59 AM, Justin Richer
<jricher@mitre.org> wrote:
		> +1 on OAuth2 header, and I also want to see
oauth2_token in URI and form
		> parameter methods.
		
		
		Good point about the query parameter names needing to be
unambiguous.
		
		_______________________________________________
		OAuth mailing list
		OAuth@ietf.org
		https://www.ietf.org/mailman/listinfo/oauth

v2.38.3 | Report a Bug | By Email | System Status