Re: [OAUTH-WG] JWT binding for OAuth 2.0

Bill Mills <wmills_92105@yahoo.com> Tue, 14 April 2015 22:06 UTC

Return-Path: <wmills_92105@yahoo.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 399FB1A8737 for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2015 15:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.509
X-Spam-Level:
X-Spam-Status: No, score=-1.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46jJGhUgxQyQ for <oauth@ietfa.amsl.com>; Tue, 14 Apr 2015 15:06:08 -0700 (PDT)
Received: from nm41.bullet.mail.bf1.yahoo.com (nm41.bullet.mail.bf1.yahoo.com [216.109.114.57]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB9761A8735 for <oauth@ietf.org>; Tue, 14 Apr 2015 15:06:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1429049166; bh=as+ltZKTp8ZdSu+kGi3eIW84T9OPHuFrBl9npNpZQ28=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=n5YNok/ogZhDsRvd2b2cjr6VcJYaCibTWqNryId0EQs7efpkHwWiEIJrl+6hzs0kC+GpPdBAB6C1rX8aR12OXWxhhsRAd/gic0HCLXvm4+06B32xnvarSa3ZvZ9q0ZKiuijjDVxcLdQssRmSHJ/ogLIEpmi5gxAGzUDKY+fUSD+ZNZ0k8IAYANBUX6u7h5B5iW9aXGekulKrBssOlvaid5EVAFRjViS7ZvMmbvORsHENjVo102r1aztPFPnX6nxMpv9Ma7pK6GcP8jTnTRUY/2tkKMHXzLJJIBvBdjwqlrnaLcWkA9eKOyk7n+cqJ/gLIp7nnyFQVJ7gpVbPBmTq8Q==
Received: from [98.139.170.179] by nm41.bullet.mail.bf1.yahoo.com with NNFMP; 14 Apr 2015 22:06:06 -0000
Received: from [98.139.212.222] by tm22.bullet.mail.bf1.yahoo.com with NNFMP; 14 Apr 2015 22:06:06 -0000
Received: from [127.0.0.1] by omp1031.mail.bf1.yahoo.com with NNFMP; 14 Apr 2015 22:06:06 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 835796.12946.bm@omp1031.mail.bf1.yahoo.com
X-YMail-OSG: WUpcdJMVM1kE2fhKBr9drYJSmfvejtbjltaPfTrETxVoU_y43_OXa0ZTkcsnlrs bFS7N.pDT60jGZZFjIzT1_1yB.n4bDR3Wh_wEAJFmZBnD9NJRThwVTrfig9J1J_a_YGHoFHOYMAe ut3na8z4CFx9mjtbYWCTD9.m1K93soJSZSOVzw09pqUrtnoCs4gdU.zKRhPykwkgk2KlPQumI9zZ huhjnfz9Sztw0XzZwDFAzbXFRd7AM.dXFvH0IfvH5U.1mUUHEu_Ue4D9bWi_A8MzAfH0dNyLmDks 72xdwWHjAhwAksdZNU87WDToMAkh1soWWZ2bx50ybXv6GCR5rABepEOTz_CjQOoYwBdZ_5lETH.7 cWzVDSLbAN5k0GlONdldeuofEZHWX9OpUOQ63k07fsrT8ISQ8q3S0tNGgdjg8zuOHhHhTbHpRGQf HdBUZjtny80L306ms9QPTXnnbeikw9J8Qzg.tLv55dohPifvotszHmt4NEqY_sYggjLv0hADva21 F9PVj5p.ObbENSH0-
Received: by 66.196.81.120; Tue, 14 Apr 2015 22:06:06 +0000
Date: Tue, 14 Apr 2015 22:06:05 +0000
From: Bill Mills <wmills_92105@yahoo.com>
To: John Bradley <ve7jtb@ve7jtb.com>, Prabath Siriwardena <prabath@wso2.com>
Message-ID: <660351144.3721997.1429049165503.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <A0FFB94C-1EDB-41B9-B1E2-6943B078145F@ve7jtb.com>
References: <A0FFB94C-1EDB-41B9-B1E2-6943B078145F@ve7jtb.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_3721996_1012661116.1429049165497"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/0zpctk5KOuac9cocnK19mVL1IbI>
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] JWT binding for OAuth 2.0
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Bill 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: Tue, 14 Apr 2015 22:06:09 -0000

Yes, Microsoft supports this on Hotmail/Outlook.com and the Outlook client supports it. 


     On Tuesday, April 14, 2015 2:42 PM, John Bradley <ve7jtb@ve7jtb.com> wrote:
   

 There is a OAuth binding to SASL https://tools.ietf.org/html/draft-ietf-kitten-sasl-oauth-19
Google supports it for IMAP/SMTP,  I think the latest iOS and OSX mail client updates use it rather than passwords for Google.I also noticed Outlook on Android using it.
The access token might be a signed or encrypted JWT itself.  I don’t know that wrapping it again necessarily helps.
Yes we should have bindings to other non http protocols.  
Is there something specific that you are looking for that is not covered by SASL?
John B.



On Apr 14, 2015, at 6:21 PM, Prabath Siriwardena <prabath@wso2.com> wrote:
At the moment we only HTTP binding to transport the access token (please correct me if not)..
This creates a dependency on the transport.
How about creating a JWT binding for OAuth 2.0..? We can transport the access token as an encrypted JWT header parameter..?


Thanks & Regards,
Prabath

Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena

Mobile : +1 650 625 7950

http://blog.facilelogin.com
http://blog.api-security.org_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth



_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth