
Return-Path: <sonicgg@gmail.com>
X-Original-To: woes@ietfc.amsl.com
Delivered-To: woes@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 00D03E06F9 for <woes@ietfc.amsl.com>; Sun, 17 Apr 2011 12:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_33=1, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUoJ30xreHV1 for <woes@ietfc.amsl.com>; Sun, 17 Apr 2011 12:53:58 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfc.amsl.com (Postfix) with ESMTP id 6F435E070B for <woes@ietf.org>; Sun, 17 Apr 2011 12:53:58 -0700 (PDT)
Received: by pzk30 with SMTP id 30so2304637pzk.31 for <woes@ietf.org>; Sun, 17 Apr 2011 12:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9PzTFNur7zGrsGfLk3BYzFsjZeuzCrShmkQd5+09T54=; b=GtZR9Uo2nkBxW3ce3Jz2Fz9ooF7S9E3TBvxuBtiJry3AZrYSvkmOrhXm9uTcjIuR9e JkmM6XE1TFa4J7+BWLjOi5TBuhoNdhNNrlsyyeZAO24St5uHPcy7XpEqTqqwa3oLw49m G7CBal0fepJA73hu7rlNj7qVhLASrwI0RJkgM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SFS6oVE3zfoTwIJmABrGQx9dddPBatbVCc/Jj8f8br/H+PpFrEPb7+f1MCh3r5MzbU 5K94ZF5rGm3mbKrMNXEYeyf2IPuqehXNkBuwZAHWPKE6NMv34LoHO6otKjSpBasAZjxu 5q/iD8SpA34cyOc6dN4/Bym4v2nizqpMYw1Bg=
MIME-Version: 1.0
Received: by 10.68.30.39 with SMTP id p7mr5549797pbh.34.1303070037770; Sun, 17 Apr 2011 12:53:57 -0700 (PDT)
Received: by 10.68.52.3 with HTTP; Sun, 17 Apr 2011 12:53:57 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11281FB7FF1@WSMSG3153V.srv.dir.telstra.com>
References: <BANLkTikAd0gbN2x8cWQQRZXwehugCE3tXw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11281FB7FF1@WSMSG3153V.srv.dir.telstra.com>
Date: Sun, 17 Apr 2011 12:53:57 -0700
Message-ID: <BANLkTi=QW23T1if4YAFgx1e7JzdaHZkdjw@mail.gmail.com>
From: Jian <sonicgg@gmail.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=bcaec520ef81b8004f04a122a237
Cc: "woes@ietf.org" <woes@ietf.org>
Subject: Re: [woes] Native JWT support in Google App Engine
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2011 19:54:00 -0000

--bcaec520ef81b8004f04a122a237
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hey James,
   You are right. In real cases, we should rely on HTTPS to transmit
certificates. Since it's just a sample app, I omit HTTPS setup for
simplicity. I will add this to the document. Thanks.

Jian

On Thu, Apr 14, 2011 at 11:03 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

>  Eric,
>
>
>
> This feels a bit like WebID <http://www.w3.org/2005/Incubator/webid/spec/=
>=96 except the client=92s public key is used to verify a message they sign=
ed,
> rather than a TLS tunnel they established. Both identify the client by a =
URI
> that delivers a certificate.
>
> Your Cloud-to-On-Premise flow, WebID, and OpenID really need to use HTTPS
> URIs as identities to be secure. However, your sample app<https://sites.g=
oogle.com/site/oauthgoog/authenticate-google-app-engine-app>has an HTTP id
> http://app-identity-java.appspot.com/certs. Was this an oversight, or
> isn=92t security of this system supposed to depend on how the app=92s
> self-signed short-lived (daily) certificate is obtained?
>
>
>
> --
>
> James Manger
>
>
>
> *From:* woes-bounces@ietf.org [mailto:woes-bounces@ietf.org] *On Behalf O=
f
> *Eric Sachs
> *Sent:* Thursday, 7 April 2011 5:43 AM
> *To:* woes@ietf.org
> *Subject:* [woes] Native JWT support in Google App Engine
>
>
>
> Google has just added native support for JWT to Google App Engine.  Here =
is
> the documentation:
>
>
> https://sites.google.com/site/oauthgoog/authenticate-google-app-engine-ap=
p
>
> Our hope is to work with other players in the cloud computing space to
> improve some elements of cloud security by using PKI, JWT & OAuth2 for
> interop between our systems.
>
>
>
> Based on past industry discussion, we wroteup a description of some of th=
e
> general interop use-cases:
>
>  https://sites.google.com/site/oauthgoog/robotaccounts/cloudtoonpremise
>
>   https://sites.google.com/site/oauthgoog/robotaccounts/onpremisetocloud
>
>  While this new feature in Google App Engine is a significant step for
> Google, we realize there is more to do on our side such as adding support
> for JWT assertions in our recently announced OAuth2 support for Google
> APIs<http://googlecode.blogspot.com/2011/03/making-auth-easier-oauth-20-f=
or-google.html>.
>  However we would prefer to get feedback from this group on a standard
> approach, including around key rotation/management.
>
>
>
> Eric Sachs
>
> Senior Product Manager, Internet Identity
>
> Google
>
>
>
> _______________________________________________
> woes mailing list
> woes@ietf.org
> https://www.ietf.org/mailman/listinfo/woes
>
>


--=20
Jian

--bcaec520ef81b8004f04a122a237
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hey James,<div>=A0 =A0You are right. In real cases, we should rely on HTTPS=
 to transmit certificates. Since it&#39;s just a sample app, I omit HTTPS s=
etup for simplicity. I will add this to the document. Thanks.<br><br></div>=
<div>
Jian</div><div><br></div><div><div class=3D"gmail_quote">On Thu, Apr 14, 20=
11 at 11:03 PM, Manger, James H <span dir=3D"ltr">&lt;<a href=3D"mailto:Jam=
es.H.Manger@team.telstra.com">James.H.Manger@team.telstra.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">





<div lang=3D"EN-AU" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Eric,=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">This =
feels a bit like
<a href=3D"http://www.w3.org/2005/Incubator/webid/spec/" target=3D"_blank">=
WebID</a> =96 except the client=92s public key is used to verify a message =
they signed, rather than a TLS tunnel they established. Both identify the c=
lient by a URI that delivers a certificate.</span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">Your =
Cloud-to-On-Premise flow, WebID, and OpenID really need to use HTTPS URIs a=
s identities to be secure. However, your
<a href=3D"https://sites.google.com/site/oauthgoog/authenticate-google-app-=
engine-app" target=3D"_blank">
sample app</a> has an HTTP id <a href=3D"http://app-identity-java.appspot.c=
om/certs" target=3D"_blank">
http://app-identity-java.appspot.com/certs</a>. Was this an oversight, or i=
sn=92t security of this system supposed to depend on how the app=92s self-s=
igned short-lived (daily) certificate is obtained?</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">--</s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">James=
 Manger</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#1F497D">=A0</=
span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt">F=
rom:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt"> <a href=3D"=
mailto:woes-bounces@ietf.org" target=3D"_blank">woes-bounces@ietf.org</a> [=
mailto:<a href=3D"mailto:woes-bounces@ietf.org" target=3D"_blank">woes-boun=
ces@ietf.org</a>]
<b>On Behalf Of </b>Eric Sachs<br>
<b>Sent:</b> Thursday, 7 April 2011 5:43 AM<br>
<b>To:</b> <a href=3D"mailto:woes@ietf.org" target=3D"_blank">woes@ietf.org=
</a><br>
<b>Subject:</b> [woes] Native JWT support in Google App Engine</span></p>
</div>
<p class=3D"MsoNormal">=A0</p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Google has just add=
ed native support for JWT to Google App Engine. =A0Here is the documentatio=
n:<br>
<br>
</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><a href=3D"https://=
sites.google.com/site/oauthgoog/authenticate-google-app-engine-app" target=
=3D"_blank"><span style=3D"color:#336633">https://sites.google.com/site/oau=
thgoog/authenticate-google-app-engine-app</span></a></span></p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Our hope is to work=
 with other players in the cloud computing space to improve some elements o=
f cloud security by using PKI,=A0JWT &amp; OAuth2 for interop between our s=
ystems.</span></p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">Based on past indus=
try discussion, we wroteup a description of some of the general interop use=
-cases:</span></p>
</div>
<blockquote style=3D"margin-left:30.0pt;margin-right:0cm;border-width:initi=
al;border-color:initial">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><a href=3D"https://=
sites.google.com/site/oauthgoog/robotaccounts/cloudtoonpremise" target=3D"_=
blank"><span style=3D"color:#336633">https://sites.google.com/site/oauthgoo=
g/robotaccounts/cloudtoonpremise</span></a></span></p>

</div>
</blockquote>
</div>
<blockquote style=3D"margin-left:30.0pt;margin-right:0cm;border-width:initi=
al;border-color:initial">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><a href=3D"https://=
sites.google.com/site/oauthgoog/robotaccounts/onpremisetocloud" target=3D"_=
blank">https://sites.google.com/site/oauthgoog/robotaccounts/onpremisetoclo=
ud</a></span></p>

</div>
</div>
</blockquote>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">While this new feat=
ure in Google App Engine is a significant step for Google, we realize there=
 is more to do on our side such as adding support for JWT assertions in our=
=A0<a href=3D"http://googlecode.blogspot.com/2011/03/making-auth-easier-oau=
th-20-for-google.html" target=3D"_blank">recently
 announced OAuth2 support for Google APIs</a>. =A0However we would prefer t=
o get feedback from this group on a standard approach, including around key=
 rotation/management.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Eric Sachs</span><span style=3D"font-size:10.0=
pt"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Senior Product Manager, Internet Identity</spa=
n><span style=3D"font-size:10.0pt"></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Google</span><span style=3D"font-size:10.0pt">=
</span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
</div>

<br>_______________________________________________<br>
woes mailing list<br>
<a href=3D"mailto:woes@ietf.org">woes@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/woes" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/woes</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Jian<br>
</div>

--bcaec520ef81b8004f04a122a237--

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: woes@ietfc.amsl.com
Delivered-To: woes@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 511A9E065C for <woes@ietfc.amsl.com>; Thu, 14 Apr 2011 23:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[AWL=-0.000,  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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tuVTZNzItOvI for <woes@ietfc.amsl.com>; Thu, 14 Apr 2011 23:03:58 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfc.amsl.com (Postfix) with ESMTP id 64CFFE073D for <woes@ietf.org>; Thu, 14 Apr 2011 23:03:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.64,217,1301839200"; d="scan'208,217";a="30312781"
Received: from unknown (HELO ipcbvi.tcif.telstra.com.au) ([10.97.217.204]) by ipoavi.tcif.telstra.com.au with ESMTP; 15 Apr 2011 16:03:49 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6316"; a="23765841"
Received: from wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) by ipcbvi.tcif.telstra.com.au with ESMTP; 15 Apr 2011 16:03:49 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) with mapi; Fri, 15 Apr 2011 16:03:48 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Eric Sachs <esachs@google.com>, "woes@ietf.org" <woes@ietf.org>
Date: Fri, 15 Apr 2011 16:03:47 +1000
Thread-Topic: [woes] Native JWT support in Google App Engine
Thread-Index: Acv0kulUHu3mpWuqT/SioKCF/IqCiQGncLeg
Message-ID: <255B9BB34FB7D647A506DC292726F6E11281FB7FF1@WSMSG3153V.srv.dir.telstra.com>
References: <BANLkTikAd0gbN2x8cWQQRZXwehugCE3tXw@mail.gmail.com>
In-Reply-To: <BANLkTikAd0gbN2x8cWQQRZXwehugCE3tXw@mail.gmail.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_255B9BB34FB7D647A506DC292726F6E11281FB7FF1WSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: Re: [woes] Native JWT support in Google App Engine
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2011 06:04:00 -0000

--_000_255B9BB34FB7D647A506DC292726F6E11281FB7FF1WSMSG3153Vsrv_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Eric,



This feels a bit like WebID<http://www.w3.org/2005/Incubator/webid/spec/> -=
 except the client's public key is used to verify a message they signed, ra=
ther than a TLS tunnel they established. Both identify the client by a URI =
that delivers a certificate.

Your Cloud-to-On-Premise flow, WebID, and OpenID really need to use HTTPS U=
RIs as identities to be secure. However, your sample app<https://sites.goog=
le.com/site/oauthgoog/authenticate-google-app-engine-app> has an HTTP id ht=
tp://app-identity-java.appspot.com/certs. Was this an oversight, or isn't s=
ecurity of this system supposed to depend on how the app's self-signed shor=
t-lived (daily) certificate is obtained?



--

James Manger



From: woes-bounces@ietf.org [mailto:woes-bounces@ietf.org] On Behalf Of Eri=
c Sachs
Sent: Thursday, 7 April 2011 5:43 AM
To: woes@ietf.org
Subject: [woes] Native JWT support in Google App Engine



Google has just added native support for JWT to Google App Engine.  Here is=
 the documentation:



https://sites.google.com/site/oauthgoog/authenticate-google-app-engine-app

Our hope is to work with other players in the cloud computing space to impr=
ove some elements of cloud security by using PKI, JWT & OAuth2 for interop =
between our systems.



Based on past industry discussion, we wroteup a description of some of the =
general interop use-cases:

https://sites.google.com/site/oauthgoog/robotaccounts/cloudtoonpremise

https://sites.google.com/site/oauthgoog/robotaccounts/onpremisetocloud

While this new feature in Google App Engine is a significant step for Googl=
e, we realize there is more to do on our side such as adding support for JW=
T assertions in our recently announced OAuth2 support for Google APIs<http:=
//googlecode.blogspot.com/2011/03/making-auth-easier-oauth-20-for-google.ht=
ml>.  However we would prefer to get feedback from this group on a standard=
 approach, including around key rotation/management.



Eric Sachs

Senior Product Manager, Internet Identity

Google




--_000_255B9BB34FB7D647A506DC292726F6E11281FB7FF1WSMSG3153Vsrv_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-AU" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Eric,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">This feels a bit like
<a href=3D"http://www.w3.org/2005/Incubator/webid/spec/">WebID</a> &#8211; =
except the client&#8217;s public key is used to verify a message they signe=
d, rather than a TLS tunnel they established. Both identify the client by a=
 URI that delivers a certificate.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">Your Cloud-to-On-Premise flow, WebID, and OpenID really need=
 to use HTTPS URIs as identities to be secure. However, your
<a href=3D"https://sites.google.com/site/oauthgoog/authenticate-google-app-=
engine-app">
sample app</a> has an HTTP id <a href=3D"http://app-identity-java.appspot.c=
om/certs">
http://app-identity-java.appspot.com/certs</a>. Was this an oversight, or i=
sn&#8217;t security of this system supposed to depend on how the app&#8217;=
s self-signed short-lived (daily) certificate is obtained?<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">--<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D">James Manger<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;
color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:
&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span lang=3D"EN=
-US" style=3D"font-size:10.0pt;
font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> woes-bounces@ietf.o=
rg [mailto:woes-bounces@ietf.org]
<b>On Behalf Of </b>Eric Sachs<br>
<b>Sent:</b> Thursday, 7 April 2011 5:43 AM<br>
<b>To:</b> woes@ietf.org<br>
<b>Subject:</b> [woes] Native JWT support in Google App Engine<o:p></o:p></=
span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Google has just added native support for =
JWT to Google App Engine. &nbsp;Here is the documentation:<br>
<br>
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><a href=3D"https://sites.google.com/site/=
oauthgoog/authenticate-google-app-engine-app" target=3D"_blank"><span style=
=3D"color:#336633">https://sites.google.com/site/oauthgoog/authenticate-goo=
gle-app-engine-app</span></a><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Our hope is to work with other players in=
 the cloud computing space to improve some elements of cloud security by us=
ing PKI,&nbsp;JWT &amp; OAuth2 for interop between our systems.<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">Based on past industry discussion, we wro=
teup a description of some of the general interop use-cases:<o:p></o:p></sp=
an></p>
</div>
<blockquote style=3D"margin-left:30.0pt;margin-right:0cm;border-width:initi=
al;
border-color:initial">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><a href=3D"https://sites.google.com/site/=
oauthgoog/robotaccounts/cloudtoonpremise" target=3D"_blank"><span style=3D"=
color:#336633">https://sites.google.com/site/oauthgoog/robotaccounts/cloudt=
oonpremise</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<blockquote style=3D"margin-left:30.0pt;margin-right:0cm;border-width:initi=
al;
border-color:initial">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><a href=3D"https://sites.google.com/site/=
oauthgoog/robotaccounts/onpremisetocloud" target=3D"_blank">https://sites.g=
oogle.com/site/oauthgoog/robotaccounts/onpremisetocloud</a><o:p></o:p></spa=
n></p>
</div>
</div>
</blockquote>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;">While this new feature in Google App Engi=
ne is a significant step for Google, we realize there is more to do on our =
side such as adding support for JWT assertions in our&nbsp;<a href=3D"http:=
//googlecode.blogspot.com/2011/03/making-auth-easier-oauth-20-for-google.ht=
ml" target=3D"_blank">recently
 announced OAuth2 support for Google APIs</a>. &nbsp;However we would prefe=
r to get feedback from this group on a standard approach, including around =
key rotation/management.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ar=
ial&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Eric Sachs</span><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Senior Product Manager, Internet Identity</span><span styl=
e=3D"font-size:10.0pt;
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Google</span><span style=3D"font-size:10.0pt;font-family:&=
quot;Arial&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_255B9BB34FB7D647A506DC292726F6E11281FB7FF1WSMSG3153Vsrv_--


Return-Path: <esachs@google.com>
X-Original-To: woes@core3.amsl.com
Delivered-To: woes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B0E13A6952 for <woes@core3.amsl.com>; Wed,  6 Apr 2011 12:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level: 
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Ly3Mqx84ZnIN for <woes@core3.amsl.com>; Wed,  6 Apr 2011 12:41:23 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 7C71D3A63CA for <woes@ietf.org>; Wed,  6 Apr 2011 12:41:23 -0700 (PDT)
Received: from wpaz1.hot.corp.google.com (wpaz1.hot.corp.google.com [172.24.198.65]) by smtp-out.google.com with ESMTP id p36Jh7SL011708 for <woes@ietf.org>; Wed, 6 Apr 2011 12:43:07 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1302118987; bh=uSgx474lvo8/yU4Tc7BxQMSl0l4=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=vHAejwcNOj+YEJXftSqA2JJ7qn/bK3Mw5sIOfmtzYms3t0bhpD+jQdY5zlG7Y8X/r Oy/zRKfzDVyEthiVVvIeQ==
Received: from qwh5 (qwh5.prod.google.com [10.241.194.197]) by wpaz1.hot.corp.google.com with ESMTP id p36Jh61L022610 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <woes@ietf.org>; Wed, 6 Apr 2011 12:43:06 -0700
Received: by qwh5 with SMTP id 5so1092517qwh.6 for <woes@ietf.org>; Wed, 06 Apr 2011 12:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=fhDVTZmNfZJjSbF7dA8W0UUCSvWJedsC8XOwTRxY/6M=; b=rxTwOx8F9yeTWqNSPhAvQ971SlKr/IZDMT2ZqJD88ZR/GkndiaypxWvQ2GzTUOWpf6 oNHLTZjqCHkTSkbWdrng==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:date:message-id:subject:from:to:content-type; b=hCP1Y6jZLiIxRH/9RE1iPhX4KyQNPco5omABIaoyenSLdgSzOef0NDqcYLV0uw84WI wdmENUk7hEurnVEVfCNA==
MIME-Version: 1.0
Received: by 10.229.99.10 with SMTP id s10mr9419qcn.123.1302118985798; Wed, 06 Apr 2011 12:43:05 -0700 (PDT)
Received: by 10.229.73.202 with HTTP; Wed, 6 Apr 2011 12:43:05 -0700 (PDT)
Date: Wed, 6 Apr 2011 12:43:05 -0700
Message-ID: <BANLkTikAd0gbN2x8cWQQRZXwehugCE3tXw@mail.gmail.com>
From: Eric Sachs <esachs@google.com>
To: woes@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba308c6a9a94d504a04533d6
X-System-Of-Record: true
Subject: [woes] Native JWT support in Google App Engine
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 19:41:24 -0000

--90e6ba308c6a9a94d504a04533d6
Content-Type: text/plain; charset=ISO-8859-1

Google has just added native support for JWT to Google App Engine.  Here is
the documentation:

https://sites.google.com/site/oauthgoog/authenticate-google-app-engine-app

Our hope is to work with other players in the cloud computing space to
improve some elements of cloud security by using PKI, JWT & OAuth2 for
interop between our systems.

Based on past industry discussion, we wroteup a description of some of the
general interop use-cases:

https://sites.google.com/site/oauthgoog/robotaccounts/cloudtoonpremise

 https://sites.google.com/site/oauthgoog/robotaccounts/onpremisetocloud

While this new feature in Google App Engine is a significant step for
Google, we realize there is more to do on our side such as adding support
for JWT assertions in our recently announced OAuth2 support for Google
APIs<http://googlecode.blogspot.com/2011/03/making-auth-easier-oauth-20-for-google.html>.
 However we would prefer to get feedback from this group on a standard
approach, including around key rotation/management.

Eric Sachs
Senior Product Manager, Internet Identity
Google

--90e6ba308c6a9a94d504a04533d6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><div><span style=3D"border-collapse:collapse;font-family:arial, sans-s=
erif;font-size:13px">Google has just added native support for JWT to Google=
 App Engine. =A0Here is the documentation:<br>
<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg=
in-left:40px;border-top-style:none;border-right-style:none;border-bottom-st=
yle:none;border-left-style:none;border-width:initial;border-color:initial;p=
adding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">


<div><a href=3D"https://sites.google.com/site/oauthgoog/authenticate-google=
-app-engine-app" style=3D"color:rgb(51, 102, 51)" target=3D"_blank">https:/=
/sites.google.com/site/oauthgoog/authenticate-google-app-engine-app</a></di=
v>


</blockquote><div>Our hope is to work with other players in the cloud compu=
ting space to improve some elements of cloud security by using PKI,=A0JWT &=
amp; OAuth2 for interop between our systems.</div><div><br></div><div>Based=
 on past industry discussion, we wroteup a description of some of the gener=
al interop use-cases:</div>


<blockquote style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg=
in-left:40px;border-top-style:none;border-right-style:none;border-bottom-st=
yle:none;border-left-style:none;border-width:initial;border-color:initial;p=
adding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">


<div><a href=3D"https://sites.google.com/site/oauthgoog/robotaccounts/cloud=
toonpremise" style=3D"color:rgb(51, 102, 51)" target=3D"_blank">https://sit=
es.google.com/site/oauthgoog/robotaccounts/cloudtoonpremise</a></div></bloc=
kquote>


</span></div><blockquote style=3D"margin-top:0px;margin-right:0px;margin-bo=
ttom:0px;margin-left:40px;border-top-style:none;border-right-style:none;bor=
der-bottom-style:none;border-left-style:none;border-width:initial;border-co=
lor:initial;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-le=
ft:0px">


<div><span style=3D"border-collapse:collapse;font-family:arial, sans-serif;=
font-size:13px"><div><a href=3D"https://sites.google.com/site/oauthgoog/rob=
otaccounts/onpremisetocloud" target=3D"_blank">https://sites.google.com/sit=
e/oauthgoog/robotaccounts/onpremisetocloud</a></div>


</span></div></blockquote><div><div style=3D"border-collapse:collapse;font-=
family:arial, sans-serif;font-size:13px">While this new feature in Google A=
pp Engine is a significant step for Google, we realize there is more to do =
on our side such as adding support for JWT assertions in our=A0<a href=3D"h=
ttp://googlecode.blogspot.com/2011/03/making-auth-easier-oauth-20-for-googl=
e.html" target=3D"_blank">recently announced OAuth2 support for Google APIs=
</a>. =A0However we would prefer to get feedback from this group on a stand=
ard approach, including around key rotation/management.</div>


<div style=3D"border-collapse:collapse;font-family:arial, sans-serif;font-s=
ize:13px"><br></div><div style=3D"border-collapse:collapse;font-family:aria=
l, sans-serif;font-size:13px"><span style=3D"font-size:small">Eric Sachs</s=
pan></div>

<div style=3D"border-collapse:collapse;font-family:arial, sans-serif;font-s=
ize:13px"><span style=3D"font-size:small">Senior Product Manager, Internet =
Identity</span></div>
<div style=3D"border-collapse:collapse;font-family:arial, sans-serif;font-s=
ize:13px"><span style=3D"font-size:small">Google</span></div></div></div><d=
iv><span style=3D"font-size:small"><br></span></div>

--90e6ba308c6a9a94d504a04533d6--


Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: woes@core3.amsl.com
Delivered-To: woes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA8053A6863; Tue,  5 Apr 2011 21:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.979
X-Spam-Level: 
X-Spam-Status: No, score=-9.979 tagged_above=-999 required=5 tests=[AWL=-0.581, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
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 a3hoB3Xtkn4F; Tue,  5 Apr 2011 21:09:01 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 3DA633A685B; Tue,  5 Apr 2011 21:09:01 -0700 (PDT)
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (157.54.7.154) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 5 Apr 2011 21:10:44 -0700
Received: from TK5EX14MBXC203.redmond.corp.microsoft.com ([169.254.3.38]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.01.0270.002; Tue, 5 Apr 2011 21:10:44 -0700
From: Mike Jones <Michael.Jones@microsoft.com>
To: "woes@ietf.org" <woes@ietf.org>, "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>
Thread-Topic: [OAUTH-WG] JWT CLI tool in PyJWT
Thread-Index: AQHL9AzB2shGLxuX70WAQ6bQp/fCHZRQOLWQ
Date: Wed, 6 Apr 2011 04:10:44 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943252CE74E@TK5EX14MBXC203.redmond.corp.microsoft.com>
References: <BANLkTimeYm4J-bvE-qVgY2=5JzL=wgHXWA@mail.gmail.com>
In-Reply-To: <BANLkTimeYm4J-bvE-qVgY2=5JzL=wgHXWA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943252CE74ETK5EX14MBXC203r_"
MIME-Version: 1.0
Cc: "Jeff Lindsay \(progrium@twilio.com\)" <progrium@twilio.com>, "oauth@ietf.org" <oauth@ietf.org>
Subject: [woes] FW: [OAUTH-WG] JWT CLI tool in PyJWT
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 04:09:02 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943252CE74ETK5EX14MBXC203r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

(Distributing to a wider audience)

Thanks for letting us know about your implementation, Jeff!

                                                            -- Mike

From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of J=
eff Lindsay
Sent: Tuesday, April 05, 2011 8:43 PM
To: OAuth WG (oauth@ietf.org)
Subject: [OAUTH-WG] JWT CLI tool in PyJWT

We use JWT a lot and end up needing it while using curl, or needing quick J=
WT generation... so I added a jwt command line utility in PyJWT. It doesn't=
 support all crypto methods yet (since PyJWT doesn't either), but it has a =
pretty nice interface for encoding/decoding.

You can install it with just "easy_install PyJWT". Here's the usage doc:

Usage: jwt [options] input

Encodes or decodes JSON Web Tokens based on input

Decoding examples:

  jwt --key=3Dsecret json.web.token
  jwt --no-verify json.web.token

Encoding requires the key option and takes space separated key/value pairs
separated by equals (=3D) as input. Examples:

  jwt --key=3Dsecret iss=3Dme exp=3D1302049071
  jwt --key=3Dsecret foo=3Dbar exp=3D+10

The exp key is special and can take an offset to current Unix time.

Options:
  --version        show program's version number and exit
  -h, --help       show this help message and exit
  -n, --no-verify  ignore signature verification on decode
  --key=3DKEY        set the secret key to sign with
  --alg=3DALG        set crypto algorithm to sign with. default=3DHS256

--_000_4E1F6AAD24975D4BA5B1680429673943252CE74ETK5EX14MBXC203r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#002060;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">(Distributing to a wider =
audience)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">Thanks for letting us kno=
w about your implementation, Jeff!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> oauth-bo=
unces@ietf.org [mailto:oauth-bounces@ietf.org]
<b>On Behalf Of </b>Jeff Lindsay<br>
<b>Sent:</b> Tuesday, April 05, 2011 8:43 PM<br>
<b>To:</b> OAuth WG (oauth@ietf.org)<br>
<b>Subject:</b> [OAUTH-WG] JWT CLI tool in PyJWT<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We use JWT a lot and end up needing it while using c=
url, or needing quick JWT generation... so I added a jwt command line utili=
ty in PyJWT. It doesn't support all crypto methods yet (since PyJWT doesn't=
 either), but it has a pretty nice
 interface for encoding/decoding.&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">You can install it with just &quot;easy_install PyJW=
T&quot;. Here's the usage doc:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Usage: jwt [options] input<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Encodes or decodes JSON Web Tokens based on input<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Decoding examples:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; jwt --key=3Dsecret json.web.token<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; jwt --no-verify json.web.token<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Encoding requires the key option and takes space sep=
arated key/value pairs<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">separated by equals (=3D) as input. Examples:<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; jwt --key=3Dsecret iss=3Dme exp=3D1302049071<=
o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; jwt --key=3Dsecret foo=3Dbar exp=3D&#43;10<o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The exp key is special and can take an offset to cur=
rent Unix time.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Options:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; --version &nbsp; &nbsp; &nbsp; &nbsp;show pro=
gram's version number and exit<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; -h, --help &nbsp; &nbsp; &nbsp; show this hel=
p message and exit<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; -n, --no-verify &nbsp;ignore signature verifi=
cation on decode<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; --key=3DKEY &nbsp; &nbsp; &nbsp; &nbsp;set th=
e secret key to sign with<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; --alg=3DALG &nbsp; &nbsp; &nbsp; &nbsp;set cr=
ypto algorithm to sign with. default=3DHS256<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943252CE74ETK5EX14MBXC203r_--


Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: woes@core3.amsl.com
Delivered-To: woes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73F1228C13C; Tue,  5 Apr 2011 10:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.284
X-Spam-Level: 
X-Spam-Status: No, score=-10.284 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_HI=-8]
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 sDPP9jpaZ34w; Tue,  5 Apr 2011 10:54:13 -0700 (PDT)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 0B3BC28C136; Tue,  5 Apr 2011 10:54:12 -0700 (PDT)
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (157.54.79.180) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 5 Apr 2011 10:55:55 -0700
Received: from TK5EX14MBXC203.redmond.corp.microsoft.com ([169.254.3.38]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.01.0270.002; Tue, 5 Apr 2011 10:55:55 -0700
From: Mike Jones <Michael.Jones@microsoft.com>
To: Bob Gregory <pathogenix@gmail.com>
Thread-Topic: [OAUTH-WG] JSON Web Token (JWT) Draft -04
Thread-Index: AcvuuIVAmFKf4FToR3mJsYxJZdQlsgAckiCAAA6ifnABIFFvAAALoptQ
Date: Tue, 5 Apr 2011 17:55:55 +0000
Message-ID: <4E1F6AAD24975D4BA5B1680429673943252CCB0C@TK5EX14MBXC203.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943252B2BB6@TK5EX14MBXC203.redmond.corp.microsoft.com> <AANLkTi=pYrucDVi+7z1RQ_A243ZXCpQzYonGLSw-MAXL@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943252BA221@TK5EX14MBXC203.redmond.corp.microsoft.com> <BANLkTi=oUbvtGvheBXGNWMPAd7eDO-G8xg@mail.gmail.com>
In-Reply-To: <BANLkTi=oUbvtGvheBXGNWMPAd7eDO-G8xg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B1680429673943252CCB0CTK5EX14MBXC203r_"
MIME-Version: 1.0
Cc: "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>, "woes@ietf.org" <woes@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "openid-specs@lists.openid.net" <openid-specs@lists.openid.net>
Subject: Re: [woes] [OAUTH-WG] JSON Web Token (JWT) Draft -04
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 17:54:25 -0000

--_000_4E1F6AAD24975D4BA5B1680429673943252CCB0CTK5EX14MBXC203r_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the candid feedback, Bob.  I agree that the specs can be more cl=
early delineated and I'll make that an editorial goal in the next round of =
revisions.  In particular, I agree that a non-JWT example should be added t=
o the JWS spec.

I intentionally kept complete JWT examples in the JWT spec, including examp=
les of the actual signing computations, so that people can verify that thei=
r JWT implementations are compatible with these values.  But I'd be open to=
 input on how complete these examples should be, versus those in the JWS sp=
ec (which describe all the signing steps in full detail, unlike the JWT dra=
ft).

                                                                -- Mike

From: Bob Gregory [mailto:pathogenix@gmail.com]
Sent: Tuesday, April 05, 2011 9:10 AM
To: Mike Jones
Cc: woes@ietf.org; oauth@ietf.org; openid-specs-ab@lists.openid.net; openid=
-specs@lists.openid.net
Subject: Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04

Hi Mike,

I'm going to start implementing draft 4 in the near future. At a cursory re=
ading, I'm concerned that splitting the specifications has not simplified t=
he language, rather it has confused the specification, and introduced gener=
alisation where there were formerly simple, specific cases.

If the long-term intent is that JWS and JWE should form composable operatio=
ns for signing and encrypting content, while JWT specifies a payload format=
, then the specifications should be more clearly delineated. The current JW=
T draft makes repeated references to headers and signatures, and includes a=
n appendix entry giving examples of signing. If JWS is the specification fo=
r signing, then the JWT draft should drop these sections.

JWT then becomes a teeny-weeny specification consisting of an overview, a t=
able for reserved claim names, the rules for verifying those claims, and so=
me notes on creating custom claims.

Likewise, if JWS is intended to be a general mechanism for signing messages=
, it would be preferable to see examples in the JWS spec which do not refer=
 to the JWT spec. Simple strings, or base64 encoded binary would make bette=
r examples for JWS, without coupling the two specifications together.

As it stands, it's impossible to implement JWT without continual cross-refe=
rence. It's much harder to gain a sense of how an implementation ought to h=
ang together than it used to be.

It's still possible for Jwt4net to be a compliant implementation of JWT wit=
hout supporting a generalised JWS implementation, but checking compliance i=
s going to be much harder. I think the next steps for the library, once I'v=
e fixed a couple of glaring holes, will be to refactor out a full JWS imple=
mentation, and treat JWT as a special case, but that adds accidental comple=
xity to what was a relatively simple library (barring my own over-complicat=
ion through stupidity).

I'm still a big fan of JWT as a standard, but I think the current spec lang=
uage is a step backwards for implementation.

 -- Bob Gregory

On Wed, Mar 30, 2011 at 4:37 PM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
Thanks, Bob.  That's great to hear!

I look forward to your feedback on the spec based upon your actual use.

                                                            -- Mike

From: Bob Gregory [mailto:pathogenix@gmail.com<mailto:pathogenix@gmail.com>=
]
Sent: Wednesday, March 30, 2011 8:36 AM
To: Mike Jones
Cc: woes@ietf.org<mailto:woes@ietf.org>; oauth@ietf.org<mailto:oauth@ietf.o=
rg>; openid-specs-ab@lists.openid.net<mailto:openid-specs-ab@lists.openid.n=
et>; openid-specs@lists.openid.net<mailto:openid-specs@lists.openid.net>

Subject: Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04

I've just uploaded a .Net implementation of JWT issuance and consumption to=
 GitHub @ https://github.com/BobFromHuddle/Jwt4Net

This is no way ready for public release, but is in use in a production syst=
em. It's based on draft 1, and I'll try and update it to draft 4 compliance=
 next week.

We're intending to provide full coverage of  the JWT spec as it matures, th=
e major block for us at the moment is the lack of a specification for the "=
jku" key encoding scheme. Until that's decided, we're using .Net's default =
serialization of private keys which is based on RFC 4050.

 -- Bob Gregory

On Wed, Mar 30, 2011 at 9:57 AM, Mike Jones <Michael.Jones@microsoft.com<ma=
ilto:Michael.Jones@microsoft.com>> wrote:
Draft -04 of the JSON Web Token (JWT)<http://self-issued.info/docs/draft-jo=
nes-json-web-token.html> specification is available.  It corrects a typo fo=
und by John Bradley in -03.

The draft is available at these locations:

*        http://www.ietf.org/internet-drafts/draft-jones-json-web-token-04.=
txt

*        http://www.ietf.org/internet-drafts/draft-jones-json-web-token-04.=
xml

*        http://self-issued.info/docs/draft-jones-json-web-token-04.html

*        http://self-issued.info/docs/draft-jones-json-web-token-04.txt

*        http://self-issued.info/docs/draft-jones-json-web-token-04.xml

*        http://self-issued.info/docs/draft-jones-json-web-token.html (will=
 point to new versions as they are posted)

*        http://self-issued.info/docs/draft-jones-json-web-token.txt (will =
point to new versions as they are posted)

*        http://self-issued.info/docs/draft-jones-json-web-token.xml (will =
point to new versions as they are posted)

*        http://svn.openid.net/repos/specifications/json_web_token/1.0/ (Su=
bversion repository, with html, txt, and html versions available)

                                                            -- Mike




--
An infinite number of mathematicians walk into a bar. The first one orders =
a beer. The second orders half a beer. The third, a quarter of a beer. The =
bartender says "You're all idiots", and pours two beers.



--
An infinite number of mathematicians walk into a bar. The first one orders =
a beer. The second orders half a beer. The third, a quarter of a beer. The =
bartender says "You're all idiots", and pours two beers.

--_000_4E1F6AAD24975D4BA5B1680429673943252CCB0CTK5EX14MBXC203r_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#002060;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">Thanks for the candid fee=
dback, Bob.&nbsp; I agree that the specs can be more clearly delineated and=
 I&#8217;ll make that an editorial goal in the next round of revisions.&nbs=
p;
 In particular, I agree that a non-JWT example should be added to the JWS s=
pec.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">I intentionally kept comp=
lete JWT examples in the JWT spec, including examples of the actual signing=
 computations, so that people can verify that their JWT
 implementations are compatible with these values.&nbsp; But I&#8217;d be o=
pen to input on how complete these examples should be, versus those in the =
JWS spec (which describe all the signing steps in full detail, unlike the J=
WT draft).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#002060"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Bob Greg=
ory [mailto:pathogenix@gmail.com]
<br>
<b>Sent:</b> Tuesday, April 05, 2011 9:10 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> woes@ietf.org; oauth@ietf.org; openid-specs-ab@lists.openid.net;=
 openid-specs@lists.openid.net<br>
<b>Subject:</b> Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Hi Mike,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I'm going to start implementing draft 4 in the near =
future. At a cursory reading, I'm concerned that splitting the specificatio=
ns has not simplified the language, rather it has confused the specificatio=
n, and introduced generalisation where
 there were formerly simple, specific cases.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the long-term intent is that JWS and JWE should f=
orm composable operations for signing and encrypting content, while JWT spe=
cifies a payload format, then the specifications should be more clearly del=
ineated. The current JWT draft makes
 repeated references to headers and signatures, and includes an appendix en=
try giving examples of signing. If JWS is the specification for signing, th=
en the JWT draft should drop these sections.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">JWT then becomes a teeny-weeny specification consist=
ing of an overview, a table for reserved claim names, the rules for verifyi=
ng those claims, and some notes on creating custom claims.&nbsp;<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Likewise, if JWS is intended to be a general mechani=
sm for signing messages, it would be preferable to see examples in the JWS =
spec which do not refer to the JWT spec. Simple strings, or base64 encoded =
binary would make better examples
 for JWS, without coupling the two specifications together.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">As it stands, it's impossible to implement JWT witho=
ut continual cross-reference. It's much harder to gain a sense of how an im=
plementation ought to hang together than it used to be.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">It's still possible for Jwt4net to be a compliant im=
plementation of JWT without supporting a generalised JWS implementation, bu=
t checking compliance is going to be much harder. I think the next steps fo=
r the library, once I've fixed a couple
 of glaring holes, will be to refactor out a full JWS implementation, and t=
reat JWT as a special case, but that adds accidental complexity to what was=
 a relatively simple library (barring my own over-complication through stup=
idity).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I'm still a big fan of JWT as a standard, but I thin=
k the current spec language is a step backwards for implementation.<o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;-- Bob Gregory<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Wed, Mar 30, 2011 at 4:37 PM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&=
gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">Thanks, Bob.&nbsp; =
That&#8217;s great to hear!</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">&nbsp;</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">I look forward to y=
our feedback on the spec based upon your actual use.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">&nbsp;</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;color:#002060">&nbsp;</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt">From:</span></b><span style=3D=
"font-size:10.0pt"> Bob Gregory [mailto:<a href=3D"mailto:pathogenix@gmail.=
com" target=3D"_blank">pathogenix@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, March 30, 2011 8:36 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:woes@ietf.org" target=3D"_blank">woes@ietf.org=
</a>; <a href=3D"mailto:oauth@ietf.org" target=3D"_blank">
oauth@ietf.org</a>; <a href=3D"mailto:openid-specs-ab@lists.openid.net" tar=
get=3D"_blank">
openid-specs-ab@lists.openid.net</a>; <a href=3D"mailto:openid-specs@lists.=
openid.net" target=3D"_blank">
openid-specs@lists.openid.net</a></span><o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04<o:p></o:p></p=
>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">I've just uploaded a .Net implementation of JWT issuance and consu=
mption to GitHub @&nbsp;<a href=3D"https://github.com/BobFromHuddle/Jwt4Net=
" target=3D"_blank">https://github.com/BobFromHuddle/Jwt4Net</a><o:p></o:p>=
</p>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This is no way ready for public release, but is in use in a produc=
tion system. It's based on draft 1, and I'll try and update it to draft 4 c=
ompliance next week.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">We're intending to provide full coverage of &nbsp;the JWT spec as =
it matures, the major block for us at the moment is the lack of a specifica=
tion for the &quot;jku&quot; key encoding scheme. Until
 that's decided, we're using .Net's default serialization of private keys w=
hich is based on RFC 4050.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;-- Bob Gregory<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">On Wed, Mar 30, 2011 at 9:57 AM, Mike Jones &lt;<a href=3D"mailto:=
Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@microsoft.com<=
/a>&gt; wrote:<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Draft -04 of the
<a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.html" ta=
rget=3D"_blank">
JSON Web Token (JWT)</a> specification is available.&nbsp; It corrects a ty=
po found by John Bradley in -03.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The draft is available at these locations:<o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://www.ietf.org/internet-drafts/draft-jones-json-web-=
token-04.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-j=
ones-json-web-token-04.txt</a><o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://www.ietf.org/internet-drafts/draft-jones-json-web-=
token-04.xml" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-j=
ones-json-web-token-04.xml</a><o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.html" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web=
-token-04.html</a><o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.txt" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-=
token-04.txt</a><o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.xml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-=
token-04.xml</a><o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.h=
tml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-to=
ken.html</a> (will point to new versions as they are posted)<o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.t=
xt" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-tok=
en.txt</a> (will point to new versions as they are posted)<o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.x=
ml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-tok=
en.xml</a> (will point to new versions as they are posted)<o:p></o:p></p>
<p><span style=3D"font-family:Symbol">&middot;</span><span style=3D"font-si=
ze:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span><a href=3D"http://svn.openid.net/repos/specifications/json_web_token=
/1.0/" target=3D"_blank">http://svn.openid.net/repos/specifications/json_we=
b_token/1.0/</a> (Subversion repository, with html, txt, and html versions =
available)<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -- Mike<o:p></o:=
p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><br>
<br clear=3D"all">
<br>
-- <br>
An infinite number of mathematicians walk into a bar. The first one orders =
a beer. The second orders half a beer. The third, a quarter of a beer. The =
bartender says &quot;You're all idiots&quot;, and pours two beers.<o:p></o:=
p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<br>
-- <br>
An infinite number of mathematicians walk into a bar. The first one orders =
a beer. The second orders half a beer. The third, a quarter of a beer. The =
bartender says &quot;You're all idiots&quot;, and pours two beers.<o:p></o:=
p></p>
</div>
</body>
</html>

--_000_4E1F6AAD24975D4BA5B1680429673943252CCB0CTK5EX14MBXC203r_--


Return-Path: <pathogenix@gmail.com>
X-Original-To: woes@core3.amsl.com
Delivered-To: woes@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6896728C11D; Tue,  5 Apr 2011 09:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.298
X-Spam-Level: 
X-Spam-Status: No, score=-3.298 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1]
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 ix4cAqaafa5k; Tue,  5 Apr 2011 09:08:30 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 4E2BF28C0DE; Tue,  5 Apr 2011 09:08:30 -0700 (PDT)
Received: by qyk29 with SMTP id 29so1760871qyk.10 for <multiple recipients>; Tue, 05 Apr 2011 09:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tAnIT6vUhE9Qgk3RwqiQYqL7tpokYYxGP+lLiyF7rYk=; b=JV/u0LrNMgdT9gqAkgwf939QNlPxfbnTnuFubo0hi/jof8/fRBYEnt9STlIHTHsR8t sDMTd7KQJLLLzApqb4nFBzgL8dofO0+jq2RtpJKVHvyADAbh4sz/ElNarqGrtHfk144f fL6xxvCH/4wlxoz2akUsKn5TUSZSdYDPlsJqA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=usa+Td6yCKjiI3yGJLppH95cMcWNt8AnRVJ0GE1oxZIGWum03Vaa8wNz2tu/fxa+hD 2lgHN3pqRjSK8v+aRfvNkmTCg445z59J6cg5UVL0jH2OhI9wSByWxQifOQU0YqKpG12k idhVz+hl/W19vlX8GzWQsDTeBEgImxidJgV3k=
MIME-Version: 1.0
Received: by 10.229.8.194 with SMTP id i2mr7596657qci.190.1302019812859; Tue, 05 Apr 2011 09:10:12 -0700 (PDT)
Received: by 10.229.11.136 with HTTP; Tue, 5 Apr 2011 09:10:12 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B1680429673943252BA221@TK5EX14MBXC203.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B1680429673943252B2BB6@TK5EX14MBXC203.redmond.corp.microsoft.com> <AANLkTi=pYrucDVi+7z1RQ_A243ZXCpQzYonGLSw-MAXL@mail.gmail.com> <4E1F6AAD24975D4BA5B1680429673943252BA221@TK5EX14MBXC203.redmond.corp.microsoft.com>
Date: Tue, 5 Apr 2011 17:10:12 +0100
Message-ID: <BANLkTi=oUbvtGvheBXGNWMPAd7eDO-G8xg@mail.gmail.com>
From: Bob Gregory <pathogenix@gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=0016e64986486f9ebf04a02e1c0d
Cc: "openid-specs-ab@lists.openid.net" <openid-specs-ab@lists.openid.net>, "woes@ietf.org" <woes@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "openid-specs@lists.openid.net" <openid-specs@lists.openid.net>
Subject: Re: [woes] [OAUTH-WG] JSON Web Token (JWT) Draft -04
X-BeenThere: woes@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Web Object Encryption and Signing \(woes\) BOF discussion list" <woes.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/woes>
List-Post: <mailto:woes@ietf.org>
List-Help: <mailto:woes-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/woes>, <mailto:woes-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2011 16:08:32 -0000

--0016e64986486f9ebf04a02e1c0d
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Mike,

I'm going to start implementing draft 4 in the near future. At a cursory
reading, I'm concerned that splitting the specifications has not simplified
the language, rather it has confused the specification, and introduced
generalisation where there were formerly simple, specific cases.

If the long-term intent is that JWS and JWE should form composable
operations for signing and encrypting content, while JWT specifies a payloa=
d
format, then the specifications should be more clearly delineated. The
current JWT draft makes repeated references to headers and signatures, and
includes an appendix entry giving examples of signing. If JWS is the
specification for signing, then the JWT draft should drop these sections.

JWT then becomes a teeny-weeny specification consisting of an overview, a
table for reserved claim names, the rules for verifying those claims, and
some notes on creating custom claims.

Likewise, if JWS is intended to be a general mechanism for signing messages=
,
it would be preferable to see examples in the JWS spec which do not refer t=
o
the JWT spec. Simple strings, or base64 encoded binary would make better
examples for JWS, without coupling the two specifications together.

As it stands, it's impossible to implement JWT without continual
cross-reference. It's much harder to gain a sense of how an implementation
ought to hang together than it used to be.

It's still possible for Jwt4net to be a compliant implementation of JWT
without supporting a generalised JWS implementation, but checking complianc=
e
is going to be much harder. I think the next steps for the library, once
I've fixed a couple of glaring holes, will be to refactor out a full JWS
implementation, and treat JWT as a special case, but that adds accidental
complexity to what was a relatively simple library (barring my own
over-complication through stupidity).

I'm still a big fan of JWT as a standard, but I think the current spec
language is a step backwards for implementation.

 -- Bob Gregory

On Wed, Mar 30, 2011 at 4:37 PM, Mike Jones <Michael.Jones@microsoft.com>wr=
ote:

>  Thanks, Bob.  That=92s great to hear!
>
>
>
> I look forward to your feedback on the spec based upon your actual use.
>
>
>
>                                                             -- Mike
>
>
>
> *From:* Bob Gregory [mailto:pathogenix@gmail.com]
> *Sent:* Wednesday, March 30, 2011 8:36 AM
> *To:* Mike Jones
> *Cc:* woes@ietf.org; oauth@ietf.org; openid-specs-ab@lists.openid.net;
> openid-specs@lists.openid.net
>
> *Subject:* Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04
>
>
>
> I've just uploaded a .Net implementation of JWT issuance and consumption =
to
> GitHub @ https://github.com/BobFromHuddle/Jwt4Net
>
>
>
> This is no way ready for public release, but is in use in a production
> system. It's based on draft 1, and I'll try and update it to draft 4
> compliance next week.
>
>
>
> We're intending to provide full coverage of  the JWT spec as it matures,
> the major block for us at the moment is the lack of a specification for t=
he
> "jku" key encoding scheme. Until that's decided, we're using .Net's defau=
lt
> serialization of private keys which is based on RFC 4050.
>
>
>
>  -- Bob Gregory
>
>
>
> On Wed, Mar 30, 2011 at 9:57 AM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> Draft -04 of the JSON Web Token (JWT)<http://self-issued.info/docs/draft-=
jones-json-web-token.html>specification is available.  It corrects a typo f=
ound by John Bradley in
> -03.
>
>
>
> The draft is available at these locations:
>
> =B7
> http://www.ietf.org/internet-drafts/draft-jones-json-web-token-04.txt
>
> =B7
> http://www.ietf.org/internet-drafts/draft-jones-json-web-token-04.xml
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token-04.htm=
l
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token-04.txt
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token-04.xml
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token.html(w=
ill point to new versions as they are posted)
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token.txt (w=
ill
> point to new versions as they are posted)
>
> =B7        http://self-issued.info/docs/draft-jones-json-web-token.xml (w=
ill
> point to new versions as they are posted)
>
> =B7        http://svn.openid.net/repos/specifications/json_web_token/1.0/=
(Subversion repository, with html, txt, and html versions available)
>
>
>
>                                                             -- Mike
>
>
>
>
>
>
> --
> An infinite number of mathematicians walk into a bar. The first one order=
s
> a beer. The second orders half a beer. The third, a quarter of a beer. Th=
e
> bartender says "You're all idiots", and pours two beers.
>



--=20
An infinite number of mathematicians walk into a bar. The first one orders =
a
beer. The second orders half a beer. The third, a quarter of a beer. The
bartender says "You're all idiots", and pours two beers.

--0016e64986486f9ebf04a02e1c0d
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Mike,</div><div><br></div><div>I&#39;m going to start implementing =
draft 4 in the near future. At a cursory reading, I&#39;m concerned that sp=
litting the specifications has not simplified the language, rather it has c=
onfused the specification, and introduced generalisation where there were f=
ormerly simple, specific cases.</div>
<div><br></div><div>If the long-term intent is that JWS and JWE should form=
 composable operations for signing and encrypting content, while JWT specif=
ies a payload format, then the specifications should be more clearly deline=
ated. The current JWT draft makes repeated references to headers and signat=
ures, and includes an appendix entry giving examples of signing. If JWS is =
the specification for signing, then the JWT draft should drop these section=
s.</div>
<div><br></div><div>JWT then becomes a teeny-weeny specification consisting=
 of an overview, a table for reserved claim names, the rules for verifying =
those claims, and some notes on creating custom claims.=A0</div><div><br>
</div><div>Likewise, if JWS is intended to be a general mechanism for signi=
ng messages, it would be preferable to see examples in the JWS spec which d=
o not refer to the JWT spec. Simple strings, or base64 encoded binary would=
 make better examples for JWS, without coupling the two specifications toge=
ther.</div>
<div><br></div><div>As it stands, it&#39;s impossible to implement JWT with=
out continual cross-reference. It&#39;s much harder to gain a sense of how =
an implementation ought to hang together than it used to be.</div><div>
<br></div><div>It&#39;s still possible for Jwt4net to be a compliant implem=
entation of JWT without supporting a generalised JWS implementation, but ch=
ecking compliance is going to be much harder. I think the next steps for th=
e library, once I&#39;ve fixed a couple of glaring holes, will be to refact=
or out a full JWS implementation, and treat JWT as a special case, but that=
 adds accidental complexity to what was a relatively simple library (barrin=
g my own over-complication through stupidity).</div>
<div><br></div><div>I&#39;m still a big fan of JWT as a standard, but I thi=
nk the current spec language is a step backwards for implementation.</div><=
div><br></div><div>=A0-- Bob Gregory</div><br><div class=3D"gmail_quote">On=
 Wed, Mar 30, 2011 at 4:37 PM, Mike Jones <span dir=3D"ltr">&lt;<a href=3D"=
mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">Thank=
s, Bob.=A0 That=92s great to hear!</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">=A0</=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">I loo=
k forward to your feedback on the spec based upon your actual use.</span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">=A0</=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#002060">=A0</=
span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">From:</span></b>=
<span style=3D"font-size:10.0pt"> Bob Gregory [mailto:<a href=3D"mailto:pat=
hogenix@gmail.com" target=3D"_blank">pathogenix@gmail.com</a>]
<br>
<b>Sent:</b> Wednesday, March 30, 2011 8:36 AM<br>
<b>To:</b> Mike Jones<br>
<b>Cc:</b> <a href=3D"mailto:woes@ietf.org" target=3D"_blank">woes@ietf.org=
</a>; <a href=3D"mailto:oauth@ietf.org" target=3D"_blank">oauth@ietf.org</a=
>; <a href=3D"mailto:openid-specs-ab@lists.openid.net" target=3D"_blank">op=
enid-specs-ab@lists.openid.net</a>; <a href=3D"mailto:openid-specs@lists.op=
enid.net" target=3D"_blank">openid-specs@lists.openid.net</a></span></p>
<div class=3D"im"><br>
<b>Subject:</b> Re: [OAUTH-WG] JSON Web Token (JWT) Draft -04</div><p></p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">I&#39;ve just uploaded a .Net implementation of JWT =
issuance and consumption to GitHub @=A0<a href=3D"https://github.com/BobFro=
mHuddle/Jwt4Net" target=3D"_blank">https://github.com/BobFromHuddle/Jwt4Net=
</a></p>
<div><div></div><div class=3D"h5">
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">This is no way ready for public release, but is in u=
se in a production system. It&#39;s based on draft 1, and I&#39;ll try and =
update it to draft 4 compliance next week.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">We&#39;re intending to provide full coverage of =A0t=
he JWT spec as it matures, the major block for us at the moment is the lack=
 of a specification for the &quot;jku&quot; key encoding scheme. Until that=
&#39;s decided, we&#39;re using .Net&#39;s default serialization
 of private keys which is based on RFC 4050.</p>
</div>
<div>
<p class=3D"MsoNormal">=A0</p>
</div>
<div>
<p class=3D"MsoNormal">=A0-- Bob Gregory</p>
<div>
<p class=3D"MsoNormal">=A0</p>
<div>
<p class=3D"MsoNormal">On Wed, Mar 30, 2011 at 9:57 AM, Mike Jones &lt;<a h=
ref=3D"mailto:Michael.Jones@microsoft.com" target=3D"_blank">Michael.Jones@=
microsoft.com</a>&gt; wrote:</p>
<div>
<div>
<p class=3D"MsoNormal">Draft -04 of the
<a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.html" ta=
rget=3D"_blank">
JSON Web Token (JWT)</a> specification is available.=A0 It corrects a typo =
found by John Bradley in -03.</p>
<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">The draft is available at these locations:</p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://www.ietf.org/internet-drafts/draft-jones-json-web-=
token-04.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-j=
ones-json-web-token-04.txt</a></p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://www.ietf.org/internet-drafts/draft-jones-json-web-=
token-04.xml" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-j=
ones-json-web-token-04.xml</a></p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.html" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web=
-token-04.html</a></p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.txt" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-=
token-04.txt</a></p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token-0=
4.xml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-=
token-04.xml</a></p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.h=
tml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-to=
ken.html</a> (will point to new versions as they are posted)</p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.t=
xt" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-tok=
en.txt</a> (will point to new versions as they are posted)</p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://self-issued.info/docs/draft-jones-json-web-token.x=
ml" target=3D"_blank">http://self-issued.info/docs/draft-jones-json-web-tok=
en.xml</a> (will point to new versions as they are posted)</p>
<p><span style=3D"font-family:Symbol">=B7</span><span style=3D"font-size:7.=
0pt">=A0=A0=A0=A0=A0=A0=A0
</span><a href=3D"http://svn.openid.net/repos/specifications/json_web_token=
/1.0/" target=3D"_blank">http://svn.openid.net/repos/specifications/json_we=
b_token/1.0/</a> (Subversion repository, with html, txt, and html versions =
available)</p>

<p class=3D"MsoNormal">=A0</p>
<p class=3D"MsoNormal">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -- Mike</p>
<p class=3D"MsoNormal">=A0</p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><br>
<br clear=3D"all">
<br>
-- <br>
An infinite number of mathematicians walk into a bar. The first one orders =
a beer. The second orders half a beer. The third, a quarter of a beer. The =
bartender says &quot;You&#39;re all idiots&quot;, and pours two beers.</p>

</div>
</div>
</div></div></div>
</div>

</blockquote></div><br><br clear=3D"all"><br>-- <br>An infinite number of m=
athematicians walk into a bar. The first one orders a beer. The second orde=
rs half a beer. The third, a quarter of a beer. The bartender says &quot;Yo=
u&#39;re all idiots&quot;, and pours two beers.<br>


--0016e64986486f9ebf04a02e1c0d--

