Re: [OAUTH-WG] Proof-Of-Possession Semantics for JSON Web Tokens (JWTs)

Chuck Mortimore <cmortimore@salesforce.com> Sun, 13 April 2014 03:39 UTC

Return-Path: <cmortimore@salesforce.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 6E0D91A01D3 for <oauth@ietfa.amsl.com>; Sat, 12 Apr 2014 20:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 6ZebvDAgq4kO for <oauth@ietfa.amsl.com>; Sat, 12 Apr 2014 20:39:27 -0700 (PDT)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id 290961A01CD for <oauth@ietf.org>; Sat, 12 Apr 2014 20:39:27 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id n16so7847111oag.41 for <oauth@ietf.org>; Sat, 12 Apr 2014 20:39:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QC/85Y0vgSVOVLASiC7+SzJ4BBtlMQeZV099LmPYYoQ=; b=idBeVNd7aIfQBJsS8MXAdzQD0ZKbMyXRXKVpe4aYS5GRPB1Xh5x9emLWRJBR3P62JE yQbQ58QRwjiL9AJlgpA0pgDalBWEotzyHhhwafn2PvX52yyaqiNQhwP7OBLv5EC0Et0Y q9cFvMx+6mbgcd/KW64i1zURnFtAraZxJJCBMcK9vsssj+fLNaCJVN3yanOedmQdJG/Y C1cB2Yn/8xHcMSytoSSJZczVSY9ccitHl6UcFlC/j28NE0lK2vdWkn162DOX4RjsGAHe w16v6w4AN6ndkQdAfGVh93wdRlbINwVS3aRAhjEVrTJofrlmhS5RPE6kXrt1rUK/37Y7 Fklw==
X-Gm-Message-State: ALoCoQlEJnC1pzreG4Cv7TNDlab1A+ZVig4hsX3pUhnL0ju9x/tYr/H80z3mgvRdLOvsFE5gn0Eo
MIME-Version: 1.0
X-Received: by 10.60.160.173 with SMTP id xl13mr27852578oeb.19.1397360365211; Sat, 12 Apr 2014 20:39:25 -0700 (PDT)
Received: by 10.76.75.169 with HTTP; Sat, 12 Apr 2014 20:39:25 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439A155FFB@TK5EX14MBXC286.redmond.corp.microsoft.com>
References: <4E1F6AAD24975D4BA5B16804296739439A132083@TK5EX14MBXC286.redmond.corp.microsoft.com> <CA+wnMn_LBojNz+LCTTQN62P_U7Rag0rot715c7XCOcXAQJmEhA@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739439A155FFB@TK5EX14MBXC286.redmond.corp.microsoft.com>
Date: Sat, 12 Apr 2014 20:39:25 -0700
Message-ID: <CA+wnMn-Dto7ySgNgMu5rkqyzfok1BWdS7WxB18ep+Uv0sFRsuw@mail.gmail.com>
From: Chuck Mortimore <cmortimore@salesforce.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=089e011764e9311f6504f6e45065
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/OEH8oCWwChgCPjyWffDJWcDXCSU
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proof-Of-Possession Semantics for JSON Web Tokens (JWTs)
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 03:39:29 -0000

Not sure it it's common yet.   The scenario I'm exploring is a client that
is paired with a server.     For example, a mobile app that's an OpenID
Connect client that is sharing it's ID Token with the server.   Both the
client and server want to be able to prove possession without sharing a
private key.

-cmort


On Sat, Apr 12, 2014 at 8:32 PM, Mike Jones <Michael.Jones@microsoft.com>wrote;wrote:

>  Is having multiple confirmation keys a common case?  I'd rather we "make
> simple things simple" than build the most general solution possible.  If an
> application really needs multiple confirmation keys, it can always defined
> a "jwks" element and the handling rules for it, and go for it...
>
>
>
>                                                             -- Mike
>
>
>
> *From:* Chuck Mortimore [mailto:cmortimore@salesforce.com]
> *Sent:* Saturday, April 12, 2014 6:12 PM
> *To:* Mike Jones
>
> *Cc:* oauth@ietf.org
> *Subject:* Re: [OAUTH-WG] Proof-Of-Possession Semantics for JSON Web
> Tokens (JWTs)
>
>
>
> Good start here Mike!
>
>
>
> One quick question - I see the "cnf" member is defined as a JWK.  Why not
> a JWK Set?    I could see use-cases for binding in multiple keys.
>
>
>
> -cmort
>
>
>
>
>
>
>
> On Tue, Apr 1, 2014 at 8:36 PM, Mike Jones <Michael.Jones@microsoft.com>
> wrote:
>
> I've written a concise Internet-Draft on proof-of-possession for JWTs with
> John Bradley and Hannes Tschofenig.  Quoting from the abstract:
>
>
>
> *This specification defines how to express a declaration in a JSON Web
> Token (JWT) that the presenter of the JWT possesses a particular key and
> that the recipient can cryptographically confirm proof-of-possession of the
> key by the presenter. This property is also sometimes described as the
> presenter being a holder-of-key.*
>
>
>
> This specification intentionally does not specify the means of
> communicating the proof-of-possession JWT, nor the messages used to
> exercise the proof key, as these are necessarily application-specific.
> Rather, this specification defines a proof-of-possession JWT data structure
> to be used by other specifications that do define those things.
>
>
>
> The specification is available at:
>
> ·
> http://tools.ietf.org/html/draft-jones-oauth-proof-of-possession-00
>
>
>
> An HTML formatted version is available at:
>
> ·
> http://self-issued.info/docs/draft-jones-oauth-proof-of-possession-00.html
>
>
>
>                                                             -- Mike
>
>
>
> P.S.  This note was also posted at http://self-issued.info/?p=1210 and as
> @selfissued.
>
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
>