Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-v2-http-mac-03.txt
William Mills <wmills_92105@yahoo.com> Thu, 28 February 2013 18:06 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 AB37F21F8B1E for <oauth@ietfa.amsl.com>; Thu, 28 Feb 2013 10:06:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[AWL=0.237, 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 VDvECQZ8wOwk for <oauth@ietfa.amsl.com>; Thu, 28 Feb 2013 10:06:06 -0800 (PST)
Received: from nm32-vm2.bullet.mail.bf1.yahoo.com (nm32-vm2.bullet.mail.bf1.yahoo.com [72.30.239.138]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD5821F8A5F for <oauth@ietf.org>; Thu, 28 Feb 2013 10:06:05 -0800 (PST)
Received: from [98.139.212.144] by nm32.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 18:06:05 -0000
Received: from [98.139.212.232] by tm1.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 18:06:05 -0000
Received: from [127.0.0.1] by omp1041.mail.bf1.yahoo.com with NNFMP; 28 Feb 2013 18:06:05 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 487990.29584.bm@omp1041.mail.bf1.yahoo.com
Received: (qmail 43209 invoked by uid 60001); 28 Feb 2013 18:06:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362074764; bh=mCXNd9Vh7jT11daU1+veM5odseX6Jfo4kulsfIRlZTw=; 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=BsPbxej8KsezKpyYEDd9e6GDVeWvLL8MzbgV7+0RfH7y3A6SED6hcQw2DNE9BLFhBEUBx//frY3J/atOBNqbNVaQ7PQ1CEQQZFBEqfn+p3z7JFZvsqK0hn74yB/IOHBmCwXP1umEul/hdXKRJK5R/ypRmHTbDrLWuZyiBkmHDYs=
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=PrnTCaTCUGc3PKEtpGBK6lcP8c5sPs0UDb9J+kcvn0fbyuv095xgFbDHV60wFhqUHPtaXLkouh6dBGO7lD+NRP701SNOeaz6T+ZnDWfj6VrqrWe35g0CY4DWuhn+D9gk2xU58rg7oCLFZYQUet+R2Zsj2yA2Lb6mkJTsqKXV64U=;
X-YMail-OSG: zUdjpcMVM1nVVZvq3rx23yZAJw7oLQBsYG9HHtGq73W2i4s 9T_y1QXRgaGNtp1UM3MnYfI9xriNtgZ3GfHRlzevzHiQNLkIhrp4AqC8ZvPj fu5A9YxsC8t0.OO.G5uj1cI9720_3.m6YfDNOxcMup8qmxsygjpvjlK3nYcr 9GwWlPJ1Xh53wnevzv2Xze35TFSbQOlPhNvFoStBL4GF_.iYJOmr9m5hhdq3 Z3zzlQo0OrWTpe61JGWkHCz5L0qBTZn60ojLQ1YDxbFo2uheOPdIhGX7RxBZ HjG_RcVLG9hLudPUVksWLENB2vRSFRXmRZbbwhmt_f3JRXTXMhiYyOmh2FxN lvd_qi8SjBDscx83Sys6BO9n65B5upxFX247PGNqWNi1bQhjSvfBnlRi8KRY Q6qpem_nn0J1mhMcoxs9U1WorSqzi1N_pG24PKc4sSFUHA4k816sxQSRU3vw cimBpEYZ2fg3RcwZzOouK0PxEhIkrpVpKqXTQFchALwV4E8ibAch08s3wOcy Mejyq_oE0dXZcJkEUwYsaP5jqIFhVcgQ4Bo4wNfIRZDk-
Received: from [209.131.62.115] by web31806.mail.mud.yahoo.com via HTTP; Thu, 28 Feb 2013 10:06:04 PST
X-Rocket-MIMEInfo: 001.001, SSBjZXJ0YWlubHkgaG9wZSBzby4KCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwogRnJvbTogU2VyZ2V5IEJlcnlvemtpbiA8c2JlcnlvemtpbkBnbWFpbC5jb20.ClRvOiBXaWxsaWFtIE1pbGxzIDx3bWlsbHNfOTIxMDVAeWFob28uY29tPiAKQ2M6ICJvYXV0aEBpZXRmLm9yZyIgPG9hdXRoQGlldGYub3JnPiAKU2VudDogVGh1cnNkYXksIEZlYnJ1YXJ5IDI4LCAyMDEzIDEwOjAyIEFNClN1YmplY3Q6IFJlOiBbT0FVVEgtV0ddIEktRCBBY3Rpb246IGRyYWZ0LWlldGYtb2F1dGgtdjItaHR0cC0BMAEBAQE-
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>
Message-ID: <1362074764.35520.YahooMailNeo@web31806.mail.mud.yahoo.com>
Date: Thu, 28 Feb 2013 10:06:04 -0800
From: William Mills <wmills_92105@yahoo.com>
To: Sergey Beryozkin <sberyozkin@gmail.com>
In-Reply-To: <512F9BB3.2010201@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1055047407-710131732-1362074764=:35520"
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: Thu, 28 Feb 2013 18:06:07 -0000
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> > *To:* 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>> > > *To:* William Mills <wmills_92105@yahoo.com > <mailto:wmills_92105@yahoo.com>> > > *Cc:* Hannes Tschofenig <hannes.tschofenig@gmx.net > <mailto:hannes.tschofenig@gmx.net>>; "oauth@ietf.org > <mailto:oauth@ietf.org>" > > <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>>" > > <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>> > > > Cc: 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>> > > > https://www.ietf.org/mailman/listinfo/oauth > > > > > > > > > > > > > > > > > > _______________________________________________ > > OAuth mailing list > > OAuth@ietf.org <mailto:OAuth@ietf.org> > > https://www.ietf.org/mailman/listinfo/oauth > > > _______________________________________________ > OAuth mailing list > 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