Re: [OAUTH-WG] trouble reading the start of sec 3 proof-of-possession-02

Brian Campbell <bcampbell@pingidentity.com> Wed, 25 March 2015 15:42 UTC

Return-Path: <bcampbell@pingidentity.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 21F2F1B2A62 for <oauth@ietfa.amsl.com>; Wed, 25 Mar 2015 08:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level:
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 LQwzQZWcgMMi for <oauth@ietfa.amsl.com>; Wed, 25 Mar 2015 08:42:43 -0700 (PDT)
Received: from na3sys009aog120.obsmtp.com (na3sys009aog120.obsmtp.com [74.125.149.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B37821A895D for <oauth@ietf.org>; Wed, 25 Mar 2015 08:42:42 -0700 (PDT)
Received: from mail-ig0-f180.google.com ([209.85.213.180]) (using TLSv1) by na3sys009aob120.postini.com ([74.125.148.12]) with SMTP ID DSNKVRLXbRkr0L1hbzahTIw/s4cYBvi6BYif@postini.com; Wed, 25 Mar 2015 08:42:42 PDT
Received: by igbud6 with SMTP id ud6so104898003igb.1 for <oauth@ietf.org>; Wed, 25 Mar 2015 08:42:36 -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:from:date :message-id:subject:to:cc:content-type; bh=B5mhur16pshv+DyeJK+qhwe8BcqiUATpa1ldaiasVGE=; b=H+zqnayMDvYLQdCSkUev2Um+2+Hak1IOzisV8UpNjP94Dq6I0XKD9SmwXmyqjnxZQd MjZqPILPhOwY3fUlnZIk1hDkcJOyUOTKDN6Tv8gLOZsYzfW42HkSTuOJ2QjOqviV/9Zx RLUPTS4XQYElpIX+a/dxqG8Gp++ITmbzbr5KCSBVaSlE3M1NLU8GfqN1xebzxwZqCy9H WZ3SeMDhT4tAkmybgFH3954Yw6hpfXWF/25w+4sYhqaE7FFn79ILyi4ssK3Vmxa0k+zG MSVqVh0ozer2ijyQUL0Xn/76tdQFdTi2o8znY+qNzM2ksYjDvq3NnTUtlQskHHMjEcAN grxQ==
X-Gm-Message-State: ALoCoQltOjrdZFdGwHLU6ErOlD78W9fWK6IBhbQgXaEqI2c+yiJgzNvTHP5ubcNNJmhh5LpOxjWYDoWHeh7ZpB1LR/9yx5jyDwnciheqTQ0JZ94QmkRp2/6V8C0RrF9m0ZvUFfS/zKmu
X-Received: by 10.107.35.70 with SMTP id j67mr14490312ioj.51.1427298156874; Wed, 25 Mar 2015 08:42:36 -0700 (PDT)
X-Received: by 10.107.35.70 with SMTP id j67mr14490303ioj.51.1427298156761; Wed, 25 Mar 2015 08:42:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.7.193 with HTTP; Wed, 25 Mar 2015 08:42:06 -0700 (PDT)
In-Reply-To: <BDAC3869-5BFA-48A8-BC67-C0B18D337E15@mit.edu>
References: <CA+k3eCSydCCrsrAdmm=5z-bQLpQZkPdJxYK3xWvfttWSbB9=uA@mail.gmail.com> <CA+k3eCRJWnEGVX94CNWBoH8ciXzxGGfSTFTbv9YqX2sard0y-g@mail.gmail.com> <BDAC3869-5BFA-48A8-BC67-C0B18D337E15@mit.edu>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 25 Mar 2015 10:42:06 -0500
Message-ID: <CA+k3eCSL+O8u9+oUU+SLO9NqQnjqsLDbdoOPQPDsntC7xHuJ0w@mail.gmail.com>
To: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="001a1140dcf29f717505121ebf31"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/d46VefaDpreo05lQwAzecj8_4NU>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] trouble reading the start of sec 3 proof-of-possession-02
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: Wed, 25 Mar 2015 15:42:48 -0000

Yeah, sorry, I misspoke (this stuff isn't easy). The presenter doesn't
confirm. The presenter presents the token along with something that proves
possession, which allows the recipient to confirm. My original grip with
both texts is that they seem to suggests that the presenter makes the
declaration in the token, which isn't true except for the special case of
issuer=presenter. In trying to clarify that, I made a different mistake.
I'm sure the draft authors will have no problem stating it clearly,
concisely and accurately though :)

On Wed, Mar 25, 2015 at 10:34 AM, Justin Richer <jricher@mit.edu> wrote:

> Agree that this language isn’t clear. The presenter doesn’t confirm the
> claim either, the presenter never even looks for it (unless the presenter
> is the issuer, which is a special and hopefully rare case). That’s why the
> key is delivered to the presenter in parallel with the token. It’s the RS
> that confirms the claim (in OAuth PoP), or whoever’s processing the
> key-protected call downstream (in something that isn’t OAuth).
>
>  — Justin
>
> On Mar 25, 2015, at 9:37 AM, Brian Campbell <bcampbell@pingidentity.com>
> wrote:
>
> There's similar wording in sec 3.3
> <https://tools.ietf.org/html/draft-ietf-oauth-proof-of-possession-02#section-3.3>
> too that seems to suggest that the presenter is the one that makes the
> claim.
>
> I think the presenter confirms the claim when it presents. It's the issuer
> that makes/asserts/declares the claim. No?
>
>   "In
>    this case, the presenter of a JWT declares that it possesses a
>    particular key and that the recipient can cryptographically confirm
>    proof-of-possession of the key by the presenter by including a "cnf"
>    (confirmation) claim in the JWT whose value is a JSON object, with
>    the JSON object containing a "kid" (key ID) member identifying the
>    key."
>
>
> On Sun, Mar 22, 2015 at 8:42 PM, Brian Campbell <
> bcampbell@pingidentity.com> wrote:
>
>> My brain hurt trying to parse the first sentence/paragraph from section 3
>> <https://tools.ietf.org/html/draft-ietf-oauth-proof-of-possession-02#section-3>:
>>
>>
>>    "The presenter of a JWT declares that it possesses a particular key
>>    and that the recipient can cryptographically confirm proof-of-
>>    possession of the key by the presenter by including a "cnf"
>>    (confirmation) claim in the JWT whose value is a JSON object, with
>>    the JSON object containing a "jwk" (JSON Web Key) or "kid" (key ID)
>>    member identifying the key."
>>
>> The issuer includes the "cnf" claim and makes the declaration not the
>> presenter. Sure, the presenter may be the issuer but that's a special case.
>>
>> Isn't it more accurate to say that it is the issuer who declares that the
>> presenter can confirm itself by some cryptographic proof-of-possession of
>> the key identified by the "cnf" claim? Or something more like that...
>>
>>
>>
>>
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>
>