Re: [OAUTH-WG] simplify authorization header?
Eran Hammer-Lahav <eran@hueniverse.com> Sun, 11 July 2010 20:03 UTC
Return-Path: <eran@hueniverse.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 874863A6A02 for <oauth@core3.amsl.com>; Sun, 11 Jul 2010 13:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.38
X-Spam-Level:
X-Spam-Status: No, score=-2.38 tagged_above=-999 required=5 tests=[AWL=0.218, 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 BOCe4B5XCssd for <oauth@core3.amsl.com>; Sun, 11 Jul 2010 13:03:27 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 9662E3A6A01 for <oauth@ietf.org>; Sun, 11 Jul 2010 13:03:27 -0700 (PDT)
Received: (qmail 3190 invoked from network); 11 Jul 2010 20:03:34 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 11 Jul 2010 20:03:34 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Sun, 11 Jul 2010 13:03:34 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>, OAuth WG <oauth@ietf.org>
Date: Sun, 11 Jul 2010 13:03:31 -0700
Thread-Topic: [OAUTH-WG] simplify authorization header?
Thread-Index: AcsgxSnLYYIRqJ1CR+alJI460nDGLwAbvikk
Message-ID: <C85F71A3.36FF4%eran@hueniverse.com>
In-Reply-To: <AANLkTik8RT67L-2SAQGxGKeSNBqW1GQm2CDniAjImPpM@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C85F71A336FF4eranhueniversecom_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] simplify 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: Sun, 11 Jul 2010 20:03:31 -0000
+1 with the exception of a new scheme name for signatures. I think we need to get to a stable draft before we can figure it out. But I would like to keep the core spec open for (small) changes until we do.
I added this to -10:
Authorization: OAuth <token> [optional extension key="value" pairs]
EHL
On 7/10/10 11:49 PM, "Brian Eaton" <beaton@google.com> wrote:
The current spec has the client create a "name='value'" syntax exactly
once, in the Authorization header. We could eliminate a fair chunk of
client code by removing the name="value" syntax and going with the
approach taken by the Basic, NTLM, and Negotiate schemes:
Authorization: OAuth2 <token>
No more escaping beyond what your HTTP library provides. Just call
setHeader("OAuth2 " + token), and you're on your merry way.
We are going to need slightly more flexibility once the signature
proposal settles down. For that, I'd suggest using a different scheme
name.
Authorization: OAuth2Signed <self-describing-signed-token>
Cheers,
Brian
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] simplify authorization header? Brian Eaton
- Re: [OAUTH-WG] simplify authorization header? Eran Hammer-Lahav
- Re: [OAUTH-WG] simplify authorization header? Brian Eaton