Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization header
David Recordon <recordond@gmail.com> Thu, 15 July 2010 17:37 UTC
Return-Path: <recordond@gmail.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 9BC153A6A55 for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.314
X-Spam-Level:
X-Spam-Status: No, score=-2.314 tagged_above=-999 required=5 tests=[AWL=0.284, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 WY-EqtuCAwQX for <oauth@core3.amsl.com>; Thu, 15 Jul 2010 10:37:45 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id AE76F3A69B4 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:37:45 -0700 (PDT)
Received: by iwn38 with SMTP id 38so1276128iwn.31 for <oauth@ietf.org>; Thu, 15 Jul 2010 10:37:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=7DFeIJhyPvfy4CU7Y5X3pFxty5429OL+JPI0tGErqFU=; b=lYb2cFm7oIfPilp5yPm+5jnFp010iwwVwNkpVEPJg9UDvK9Sh76W1rQEk/5yGQVaeb LxAxtZ2m5dnDZwcfWJh4Tar/zqz9ObqmYlEJaoVqH6zWNsLdIxkkPVg31P7bFMyPCf8C sGyF8ChWBmjoSfuPJFSrtGEiSwP6BivK7MaOk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=MTyEL80hhPKSE7Jo/Ybn4u6PVDEAdDq4qcrSUMw30S8ZJiYAVGtgIsYf4ErU2Xd3xg 6C+tutauHHY3QEhlWzTDqKWRMnmyxatye5MKnYbEI8tUvutt6Dj5ldP27DQz8rMuaKcZ q8sDRcMh8D58jV3wWZXr8fQDQdPVOHhyauMHE=
MIME-Version: 1.0
Received: by 10.231.150.16 with SMTP id w16mr19987108ibv.42.1279215476227; Thu, 15 Jul 2010 10:37:56 -0700 (PDT)
Received: by 10.231.196.88 with HTTP; Thu, 15 Jul 2010 10:37:56 -0700 (PDT)
In-Reply-To: <AANLkTildz62l2Me26Dlrv5nNmp8Z3P8JD1K-ChcWc5IO@mail.gmail.com>
References: <AANLkTim6az--AdwmEoew2pz3kEjhc_GyEaiyo_0UhSRr@mail.gmail.com> <1279205969.18579.55.camel@localhost.localdomain> <AANLkTildz62l2Me26Dlrv5nNmp8Z3P8JD1K-ChcWc5IO@mail.gmail.com>
Date: Thu, 15 Jul 2010 10:37:56 -0700
Message-ID: <AANLkTill8k-fUFt-IZLWdZinScj4fSBoI4rAiAf1PrYR@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: Brian Eaton <beaton@google.com>
Content-Type: multipart/alternative; boundary="0016e68dda0d0d3f1d048b7090a1"
Cc: "oauth@ietf.org" <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:37:46 -0000
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 >
- [OAUTH-WG] OAuth vs OAuth2 in Authorization header Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Manger, James H
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Blaine Cook
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Lukas Rosenstock
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… David Recordon
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Brian Eaton
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Luke Shepard
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… John Kemp
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… David Recordon
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… John Kemp
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Eran Hammer-Lahav
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Marius Scurtescu
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Justin Richer
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Naitik Shah
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Torsten Lodderstedt
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Naitik Shah
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… William Mills
- Re: [OAUTH-WG] OAuth vs OAuth2 in Authorization h… Manger, James H