[OAUTH-WG] GOOG1
"Manger, James H" <James.H.Manger@team.telstra.com> Thu, 14 October 2010 23:27 UTC
Return-Path: <James.H.Manger@team.telstra.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 D144D3A69AE for <oauth@core3.amsl.com>; Thu, 14 Oct 2010 16:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.488
X-Spam-Level:
X-Spam-Status: No, score=-0.488 tagged_above=-999 required=5 tests=[AWL=0.412, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 h2TsJkQGP7Vd for <oauth@core3.amsl.com>; Thu, 14 Oct 2010 16:27:55 -0700 (PDT)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by core3.amsl.com (Postfix) with ESMTP id CC9DD3A6973 for <oauth@ietf.org>; Thu, 14 Oct 2010 16:27:54 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.57,333,1283695200"; d="scan'208,217"; a="14204148"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipocni.tcif.telstra.com.au with ESMTP; 15 Oct 2010 10:29:14 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6136"; a="11306701"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcani.tcif.telstra.com.au with ESMTP; 15 Oct 2010 10:29:13 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Fri, 15 Oct 2010 09:29:12 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Date: Fri, 15 Oct 2010 09:29:11 +1000
Thread-Topic: GOOG1
Thread-Index: Actr95smpefG+gMoRAuEh9Fz8rmVvg==
Message-ID: <255B9BB34FB7D647A506DC292726F6E112705633B6@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E112705633B6WSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: [OAUTH-WG] GOOG1
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, 14 Oct 2010 23:27:55 -0000
I noticed that a new HTTP authentication scheme has been defined: GOOG1. http://code.google.com/apis/storage/docs/developer-guide.html#authentication Is this a candidate for the signature spec? It should be the sort of scheme that OAuth core can provide credentials for (access key & secret) without the scheme needing to know about OAuth. [It is an HMAC-SHA1; carried in the Authorization header; calculated over the method (eg GET), date, content-type, URI path (but not host or scheme), MD5-hash of request body (optional), and some proprietary headers (eg access-control details). It looks very similar to the Amazon S3 scheme.] -- James Manger
- [OAUTH-WG] GOOG1 Manger, James H
- Re: [OAUTH-WG] GOOG1 Marius Scurtescu