IETF Logo Mail Archive

Re: [OAUTH-WG] FW: MAC: Cookie name or value as MAC key id

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 15 June 2011 02:06 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322551F0C52 for <oauth@ietfa.amsl.com>; Tue, 14 Jun 2011 19:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sH5iB1l5drvA for <oauth@ietfa.amsl.com>; Tue, 14 Jun 2011 19:06:19 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id 3D2E91F0C4F for <oauth@ietf.org>; Tue, 14 Jun 2011 19:06:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.65,368,1304258400"; d="scan'208";a="36433123"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 15 Jun 2011 12:06:17 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6377"; a="28963255"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcavi.tcif.telstra.com.au with ESMTP; 15 Jun 2011 12:06:17 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Wed, 15 Jun 2011 12:06:16 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: oauth <oauth@ietf.org>
Date: Wed, 15 Jun 2011 12:06:15 +1000
Thread-Topic: [OAUTH-WG] FW: MAC: Cookie name or value as MAC key id
Thread-Index: AcwqtV8PsbK7w93mR6a7bIH6yaYxlwACGJ1wAA++2SA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E112868E5D71@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E112868E56E3@WSMSG3153V.srv.dir.telstra.com> <BANLkTikWXZSi0cVfAt0b-hM8B0k7ij5c2g@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E7234475E7747B3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E7234475E7747B3@P3PW5EX1MB01.EX1.SECURESERVER.NET>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] FW: MAC: Cookie name or value as MAC key id
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Wed, 15 Jun 2011 02:06:20 -0000

>>> Perhaps omitting the id parameter from the Authorization header
>>> would be an even better approach [when a cookie provides the key id]

>> Yeah, I've often wondered whether we should remove the id parameter
>> from the Authorization header.  My understanding is that it plays some
>> important role in the OAuth instantiation of the protocol.  There's also the
>> question about what to do when you have multiple cookies with MAC
>> attributes.  In that case, having the id to disambiguate seems useful.

> With OAuth 2.0, the id is the access token. With cookies, it makes it clear which MAC cookie is > > being used. It's required.

How does the server know if a particular request with a "Authorization: MAC ..." header is using credentials from OAuth 2.0 or from Set-Cookie?

P.S. id=<cookie-name> is not ideal for indicating which MAC cookie is being used as there can be multiple cookies with the same cookie-name (eg set from sibling domains).

--
James Manger

v2.23.0 | Report a Bug | By Email