Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt
William Mills <wmills_92105@yahoo.com> Fri, 01 March 2013 14:56 UTC
Return-Path: <wmills_92105@yahoo.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 76F7E1F0D0B for <oauth@ietfa.amsl.com>; Fri, 1 Mar 2013 06:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level:
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 E-j44cZnFWp1 for <oauth@ietfa.amsl.com>; Fri, 1 Mar 2013 06:56:21 -0800 (PST)
Received: from nm33-vm2.bullet.mail.bf1.yahoo.com (nm33-vm2.bullet.mail.bf1.yahoo.com [72.30.239.202]) by ietfa.amsl.com (Postfix) with ESMTP id A86E71F0D08 for <oauth@ietf.org>; Fri, 1 Mar 2013 06:56:20 -0800 (PST)
Received: from [98.139.212.146] by nm33.bullet.mail.bf1.yahoo.com with NNFMP; 01 Mar 2013 14:56:20 -0000
Received: from [98.139.212.240] by tm3.bullet.mail.bf1.yahoo.com with NNFMP; 01 Mar 2013 14:56:20 -0000
Received: from [127.0.0.1] by omp1049.mail.bf1.yahoo.com with NNFMP; 01 Mar 2013 14:56:20 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 138001.40055.bm@omp1049.mail.bf1.yahoo.com
Received: (qmail 3760 invoked by uid 60001); 1 Mar 2013 14:56:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362149779; bh=EbyZauqMYjrVWHipiYYf5DbthP1P1c6QTLOIUPFLgmE=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=GwCz5bcms6bZCOQqlNokvBTfZ70/LdglTwAnRNMEBdx7o3Cc7YCu0eHutNXfk2ZKT+4nGLVkWgG89yZz6Ap2b4J4Uk0mt1ijlELsAIF/agAevOyGdqWJYJI8fhRYJLcByS3IjWhRiOjKaJw23qtiHgRvD6E5RU2rdZEzmjXxMgY=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=JbgvsNNau+nvKe7t4RHBo1goH0H2ORkdNZ5HU+f0oDe0yiJln2gaCbZ18GUq2mkSA5ctjzLq3XOTIFwz6NxRWAbtiY8FDli0Ohpbn3Zu0Bfdq/oG+QUOGavxTs9aeZ17EJANJyA7aTszp6T9UG70oad+Utp4lXuh0LY4Gdyxd5U=;
X-YMail-OSG: qqkRUVoVM1k7xUkrPzT7zPoI96x9sA17y7CaWdWJQ3osI35 1Nm34iZ.tSPft18XP48nZ6jEcNO6d4cyJdumBmIwsE0OBURm7mzoxNeooviP 7meNjdm0l3KsPFfQbpxyGSe8MN7_KEcHnJSKHEdPsvSZqq.MaC7R_FAMpZeL WFCaNnYd27def_QbW.kJbepR9mxVX.BXttx_aPJEZx7.CI4HO9d2x2QEOXub 8y2cFbj49Cfzfabl0s09ueGMeqrr7VFy0WuNVJBOCL8FURtdESq0FCaYh9ZC eYnVZODEH7fRLAhCY.PgrIb5iM.TrVmFz_zbgGNrmQa3AXUeOXRT2Rlt5wWY pYt7H_Pxw_UmK2lvghA74hDLkHcp.p9ORZDTbtL2nAAv_M4AqaHNKCRhOvw_ o_31TidDN2ftES0EUiRyzGuAbE2j3A6G25J.8EgQBzI_zoSv9aNZpTpR4A99 Xrg5_YHvfEpDc4Vu2EyanqSn9LjAPVxyQuuHyciWYreDtMLj3qJB0wQkpP7I pfRR55mxfDRzS8MsE.xDOqAcn1uaH4OSLaXdMgO83UcEuhE9I9LUXi5uBLb4 h
Received: from [209.131.62.115] by web31807.mail.mud.yahoo.com via HTTP; Fri, 01 Mar 2013 06:56:19 PST
X-Rocket-MIMEInfo: 001.001, VGhlIG5ldyBzaWduYXR1cmUgYmFzZSBzdHJpbmcgc3R1ZmYgc3RpbGwgbmVlZHMgd29yaywgSSB3YW50ZWQgdG8gdGFja2xlIG1vcmUgbWFqb3IgcmVzdHJ1Y3R1cmluZyBmaXJzdC4gwqBJIHdhbnQgdG8gcHVsbCBhbGwgb2YgdGhvc2UgdGhpbmdzIG91dCBvZiB0aGUgcXVlcnkgc3RyaW5nLiDCoAoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCiBGcm9tOiBTZXJnZXkgQmVyeW96a2luIDxzYmVyeW96a2luQGdtYWlsLmNvbT4KVG86IFdpbGxpYW0gTWlsbHMgPHdtaWxsc185MjEwNUB5YWhvby4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.135.514
References: <20130225124642.7425.65145.idtracker@ietfa.amsl.com> <1361956373.9883.YahooMailNeo@web31807.mail.mud.yahoo.com> <21030204-8EA7-4FB0-9DD3-2B6C8CA57E02@gmx.net> <1362057295.36069.YahooMailNeo@web31809.mail.mud.yahoo.com> <512F8E1D.2060408@gmail.com> <1362073743.15800.YahooMailNeo@web31802.mail.mud.yahoo.com> <512F9BB3.2010201@gmail.com> <1362074764.35520.YahooMailNeo@web31806.mail.mud.yahoo.com> <5130962C.9090408@gmail.com>
Message-ID: <1362149779.70391.YahooMailNeo@web31807.mail.mud.yahoo.com>
Date: Fri, 01 Mar 2013 06:56:19 -0800
From: William Mills <wmills_92105@yahoo.com>
To: Sergey Beryozkin <sberyozkin@gmail.com>
In-Reply-To: <5130962C.9090408@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-125733401-1451799642-1362149779=:70391"
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: William Mills <wmills_92105@yahoo.com>
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: Fri, 01 Mar 2013 14:56:22 -0000
The new signature base string stuff still needs work, I wanted to tackle more major restructuring first. I want to pull all of those things out of the query string. ________________________________ From: Sergey Beryozkin <sberyozkin@gmail.com> To: William Mills <wmills_92105@yahoo.com> Cc: "oauth@ietf.org" <oauth@ietf.org> Sent: Friday, March 1, 2013 3:51 AM Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt I'm looking at [1] and I honestly don't follow what would adding JSON structure bring to the table, the text there is quite straight-forward, and the 'sorting' variable is not even there, may be, only if headers are *optionally* included when calculating 'mac'. Are you indirectly referring to the idea of OAuth2 servers supporting an OAuth1-style tokens which was proposed in the other thread by any chance, as you mention "oath_..." parameters ? In that context, using JWT extension may work, not really sure, but in context of [1] - I don't understand where it would fit in Thanks, Sergey [1] http://datatracker.ietf.org/doc/draft-ietf-oauth-v2-http-mac/?include_text=1 On 28/02/13 18:06, William Mills wrote: > I certainly hope so. > > ------------------------------------------------------------------------ > *From:* Sergey Beryozkin <sberyozkin@gmail.com> > *To:* William Mills <wmills_92105@yahoo.com> > *Cc:* "oauth@ietf.org" <oauth@ietf.org> > *Sent:* Thursday, February 28, 2013 10:02 AM > *Subject:* Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt > > On 28/02/13 17:49, William Mills wrote: > > The JWT replaces the oauth_token data element in the old MAC stuff. I > > just want to take all the other oauth_* variables and stuff them in a > > separate JSON object and completely kill the "fun with sorting > > variables" when the oauth_* things can be carried in the query string or > > header or post body. > As far as the client accessing RS is concerned, should it be limited to > using a header, same as for other OAuth2 tokens ? > > Cheers, Sergey > > > > > ------------------------------------------------------------------------ > > *From:* Sergey Beryozkin <sberyozkin@gmail.com > <mailto:sberyozkin@gmail.com>> > > *To:* oauth@ietf.org <mailto:oauth@ietf.org> > > *Sent:* Thursday, February 28, 2013 9:04 AM > > *Subject:* Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt > > > > Hi > > On 28/02/13 13:14, William Mills wrote: > > > I'm actually advocating that we change MAC to be a JWT extension. > > IMHO, having a simpler option, plus, going forward, a possible JWT > > profile (client to RS path) would work better - > > > > Why would JWT completely take over ? May be it should be possible indeed > > to have it as a JWT extension - should it be part of the relevant JWT > > assertion spec, where JWT is used as a possible grant ? > > > > Thanks, Sergey > > > > > > > ------------------------------------------------------------------------ > > > *From:* Hannes Tschofenig <hannes.tschofenig@gmx.net > <mailto:hannes.tschofenig@gmx.net> > > <mailto:hannes.tschofenig@gmx.net <mailto:hannes.tschofenig@gmx.net>>> > > > *To:* William Mills <wmills_92105@yahoo.com > <mailto:wmills_92105@yahoo.com> > > <mailto:wmills_92105@yahoo.com <mailto:wmills_92105@yahoo.com>>> > > > *Cc:* Hannes Tschofenig <hannes.tschofenig@gmx.net > <mailto:hannes.tschofenig@gmx.net> > > <mailto:hannes.tschofenig@gmx.net > <mailto:hannes.tschofenig@gmx.net>>>; "oauth@ietf.org > <mailto:oauth@ietf.org> > > <mailto:oauth@ietf.org <mailto:oauth@ietf.org>>" > > > <oauth@ietf.org <mailto:oauth@ietf.org> <mailto:oauth@ietf.org > <mailto:oauth@ietf.org>>> > > > *Sent:* Thursday, February 28, 2013 2:28 AM > > > *Subject:* Re: [OAUTH-WG] I-D Action: > draft-ietf-oauth-v2-http-mac-03.txt > > > > > > Hi Bill, > > > > > > I believe you are misreading the document. In > > > draft-ietf-oauth-v2-http-mac the client still uses the MAC when it > > > accesses a protected resource. > > > The only place where the JWT comes into the picture is with the > > > description of the access token. This matters from a key distribution > > > point of view. The session key for the MAC is included in the encrypted > > > JWT. The JWT is encrypted by the authorization server and decrypted by > > > the resource server. > > > > > > Information about how header fields get included in the MAC is > described > > > in Section 5. > > > > > > The nonce isn't killed it is just called differently: seq-nr. The stuff > > > in the original MAC specification actually wasn't a nonce (from the > > > semantic point of view). > > > The extension parameter is there implicitly by allowing additional > > > header fields to be included in the MAC computation. > > > > > > I need to look at the port number field again. > > > > > > Ciao > > > Hannes > > > > > > On Feb 27, 2013, at 11:12 AM, William Mills wrote: > > > > > > > Just read the draft quickly. > > > > > > > > Since we're now leaning on JWT do we need to include the token in > > > this? Why not just make an additional "Envelope MAC" thing and have the > > > signature include the 3 JWT parts in the signature base string? That > > > object then just becomes a JSON container for the kid, timestamp, > > > signature method, signature etc. That thing then is a 4th base64 > encoded > > > JSON thing in the auth header. > > > > > > > > How header fields get included in the signature needs definition. > > > > > > > > Why did you kill the port number, nonce, and extension parameter out > > > of the signature base string? > > > > > > > > The BNF appears to have no separators between values. > > > > > > > > -bill > > > > > > > > > > > > From: "internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> > > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>>" > > > <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> > > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> > <mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>>> > > > > To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org> > <mailto:i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>> > > <mailto:i-d-announce@ietf.org <mailto:i-d-announce@ietf.org> > <mailto:i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>> > > > > Cc: oauth@ietf.org <mailto:oauth@ietf.org> <mailto:oauth@ietf.org > <mailto:oauth@ietf.org>> <mailto:oauth@ietf.org <mailto:oauth@ietf.org> > > <mailto:oauth@ietf.org <mailto:oauth@ietf.org>>> > > > > Sent: Monday, February 25, 2013 4:46 AM > > > > Subject: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt > > > > > > > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > > > directories. > > > > This draft is a work item of the Web Authorization Protocol Working > > > Group of the IETF. > > > > > > > > Title : OAuth 2.0 Message Authentication Code (MAC) Tokens > > > > Author(s) : Justin Richer > > > > William Mills > > > > Hannes Tschofenig > > > > Filename : draft-ietf-oauth-v2-http-mac-03.txt > > > > Pages : 26 > > > > Date : 2013-02-25 > > > > > > > > Abstract: > > > > This specification describes how to use MAC Tokens in HTTP requests > > > > to access OAuth 2.0 protected resources. An OAuth client willing to > > > > access a protected resource needs to demonstrate possession of a > > > > crytographic key by using it with a keyed message digest function to > > > > the request. > > > > > > > > The document also defines a key distribution protocol for obtaining a > > > > fresh session key. > > > > > > > > > > > > The IETF datatracker status page for this draft is: > > > > https://datatracker.ietf.org/doc/draft-ietf-oauth-v2-http-mac > > > > > > > > There's also a htmlized version available at: > > > > http://tools.ietf.org/html/draft-ietf-oauth-v2-http-mac-03 > > > > > > > > A diff from the previous version is available at: > > > > http://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-v2-http-mac-03 > > > > > > > > > > > > Internet-Drafts are also available by anonymous FTP at: > > > > ftp://ftp.ietf.org/internet-drafts/ > > > > > > > > _______________________________________________ > > > > OAuth mailing list > > > > OAuth@ietf.org <mailto:OAuth@ietf.org> <mailto:OAuth@ietf.org > <mailto:OAuth@ietf.org>> <mailto:OAuth@ietf.org <mailto:OAuth@ietf.org> > > <mailto:OAuth@ietf.org <mailto:OAuth@ietf.org>>> > > > > https://www.ietf.org/mailman/listinfo/oauth > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > OAuth mailing list > > > OAuth@ietf.org <mailto:OAuth@ietf.org> <mailto:OAuth@ietf.org > <mailto:OAuth@ietf.org>> > > > https://www.ietf.org/mailman/listinfo/oauth > > > > > > _______________________________________________ > > OAuth mailing list > > OAuth@ietf.org <mailto:OAuth@ietf.org> <mailto:OAuth@ietf.org > <mailto:OAuth@ietf.org>> > > https://www.ietf.org/mailman/listinfo/oauth > > > > > >
- [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-m… internet-drafts
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Hannes Tschofenig
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Antonio Sanso
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Justin Richer
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… John Bradley
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Justin Richer
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Phil Hunt
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Sergey Beryozkin
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… William Mills
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-ht… Sergey Beryozkin