Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-pop-architecture-06.txt

Brian Campbell <bcampbell@pingidentity.com> Wed, 25 November 2015 17:15 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 A18DE1A6F3A for <oauth@ietfa.amsl.com>; Wed, 25 Nov 2015 09:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.368
X-Spam-Level:
X-Spam-Status: No, score=-1.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=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 q7bYDb2IeYTi for <oauth@ietfa.amsl.com>; Wed, 25 Nov 2015 09:15:24 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 269411A6F3B for <oauth@ietf.org>; Wed, 25 Nov 2015 09:15:24 -0800 (PST)
Received: by ioc74 with SMTP id 74so60010786ioc.2 for <oauth@ietf.org>; Wed, 25 Nov 2015 09:15:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=F6a9PH97uA0Z/RXACTIAl3iIlJnoJ+fBzncjVQxyefI=; b=IE0xJnHhxzXgEc84fRo+enRQvNEJpimyWyZwoxgwGCqzA0SKKGXh/4lhDEwFndbeVS K4bZgn9vQ8Jti/vO82PfxrkZtpyz7Yom1kLuUtaspcqYtro7dxwohdDwVjA0Nu1HAV8/ u0pVm7j86bOs+VowbHs3VX920V02pZXYpTsjI=
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=F6a9PH97uA0Z/RXACTIAl3iIlJnoJ+fBzncjVQxyefI=; b=kICOCVWc9JTprAEHT1s9pGhV3lMyYXh4GMOAdzDPj3MjG7fyMir1B7uPXhjpYMg4Tw ye87UHtBur1qYorX5b+TBta/o05ycP7Xi/KN4m71igC68HyxyLDTxgRU6L5PGqsfO2Ns jBCkSLrtP4x+3rwja6y8hRVYwiQCCuH0HmhreQIPy5JbRrWM3PjigPJAIVp0TkzFPIMo gJiGGkz2FocuIBOzb0H5VyJ+zVy8CDFjMbozcedVN5N3CwdRTA2PfciDcQv+UwDDVSfj 2EOihlYIJEjLW9L3C8ft++aCPsmAFejrNUw9wY1JQyWLEVzpyL18Kht5rN54k9i+dWPw 7U+A==
X-Gm-Message-State: ALoCoQmcKJW9Jb7hRQJlx98edti7YKrR7BqGEP9q0zoB5BsNQ8iY/Ts9/GYPFz86fqQAwNf73P2l
X-Received: by 10.107.7.24 with SMTP id 24mr40492328ioh.48.1448471723343; Wed, 25 Nov 2015 09:15:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.23.133 with HTTP; Wed, 25 Nov 2015 09:14:53 -0800 (PST)
In-Reply-To: <16FAD3AC-CFB8-46D5-A12E-436E902EA439@oracle.com>
References: <20151124200512.20833.28463.idtracker@ietfa.amsl.com> <F787FB76-5C8D-45F5-8A81-E430E75A0455@oracle.com> <CA+k3eCSeOyc2HMY+sK9rSjxkSAvNPWqwKyJNjDZAaCu2Stqk=w@mail.gmail.com> <16FAD3AC-CFB8-46D5-A12E-436E902EA439@oracle.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Wed, 25 Nov 2015 10:14:53 -0700
Message-ID: <CA+k3eCT1+=2zysgbaKEmWCkQmsKyjr9KbghgmOVYUSC1qLfjbg@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary=001a113f8b8289b9870525609aa7
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/z5lrd8zVFWo0IxQj8SEamcjICWM>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-pop-architecture-06.txt
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: <https://mailarchive.ietf.org/arch/browse/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 Nov 2015 17:15:26 -0000

Where does it say that?



On Wed, Nov 25, 2015 at 8:44 AM, Phil Hunt <phil.hunt@oracle.com> wrote:

> Except that later on we require the token be signed and the client verify
> that signed token. IOW mutual pop.
>
> Phil
>
> On Nov 25, 2015, at 07:30, Brian Campbell <bcampbell@pingidentity.com>
> wrote:
>
> Looking at the diff I noticed the following new text, which seems to
> conflate bearer/PoP and opaqueness to the client. A client demonstrating
> proof-of-possession of some key is orthogonal to the client being able to
> parse and understand the access token itself.
>
> "In contrast to bearer tokens [RFC6750] which call for tokens that are
> opaque to OAuth 2.0 clients, this specification defines the requirements
> for proof-of-possession ("PoP") tokens that may be parsed and verified by
> OAuth 2.0 clients and relying parties."
>
> On Tue, Nov 24, 2015 at 1:07 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
>
>> This draft addresses review comments from Kathleen and Erik raised since
>> the last draft.
>>
>> It may not include some of the discussion from yesterday/today.  I will
>> add that as the group decides.
>>
>> Cheers,
>>
>> Phil
>>
>> @independentid
>> www.independentid.com
>> phil.hunt@oracle.com
>>
>> > On Nov 24, 2015, at 12:05 PM, internet-drafts@ietf.org wrote:
>> >
>> >
>> > A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> > This draft is a work item of the Web Authorization Protocol Working
>> Group of the IETF.
>> >
>> >        Title           : OAuth 2.0 Proof-of-Possession (PoP) Security
>> Architecture
>> >        Authors         : Phil Hunt
>> >                          Justin Richer
>> >                          William Mills
>> >                          Prateek Mishra
>> >                          Hannes Tschofenig
>> >       Filename        : draft-ietf-oauth-pop-architecture-06.txt
>> >       Pages           : 23
>> >       Date            : 2015-11-24
>> >
>> > Abstract:
>> >   The OAuth 2.0 bearer token specification, as defined in RFC 6750,
>> >   allows any party in possession of a bearer token (a "bearer") to get
>> >   access to the associated resources (without demonstrating possession
>> >   of a cryptographic key).  To prevent misuse, bearer tokens must be
>> >   protected from disclosure in transit and at rest.
>> >
>> >   Some scenarios demand additional security protection whereby a client
>> >   needs to demonstrate possession of cryptographic keying material when
>> >   accessing a protected resource.  This document motivates the
>> >   development of the OAuth 2.0 proof-of-possession security mechanism.
>> >
>> >
>> > The IETF datatracker status page for this draft is:
>> > https://datatracker.ietf.org/doc/draft-ietf-oauth-pop-architecture/
>> >
>> > There's also a htmlized version available at:
>> > https://tools.ietf.org/html/draft-ietf-oauth-pop-architecture-06
>> >
>> > A diff from the previous version is available at:
>> > https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-pop-architecture-06
>> >
>> >
>> > Please note that it may take a couple of minutes from the time of
>> submission
>> > until the htmlized version and diff are available at tools.ietf.org.
>> >
>> > Internet-Drafts are also available by anonymous FTP at:
>> > ftp://ftp.ietf.org/internet-drafts/
>> >
>> > _______________________________________________
>> > 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
>>
>
>
>
> --
> [image: Ping Identity logo] <https://www.pingidentity.com/>
> Brian Campbell
> Distinguished Engineer
> Ping Identity
> @ bcampbell@pingidentity.com [image: phone] +1 720.317.2061 [image:
> twitter] @pingidentity Connect with us!
> <https://www.pingidentity.com/>[image: pingidentity.com]
> <https://www.pingidentity.com/>
> <https://ping.force.com/Support/PingIdentityCommunityHome>[image:
> pingidentity.com]
> <https://ping.force.com/Support/PingIdentityCommunityHome>
> [image: twitter logo]
> <http://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm> [image:
> twitter logo] <https://twitter.com/pingidentity> [image: youtube logo]
> <https://www.youtube.com/user/PingIdentityTV> [image: LinkedIn logo]
> <https://www.linkedin.com/company/21870> [image: Facebook logo]
> <https://www.facebook.com/pingidentitypage> [image: Google+ logo]
> <https://plus.google.com/u/0/114266977739397708540> [image: slideshare
> logo] <http://www.slideshare.net/PingIdentity> [image: flipboard logo]
> <http://flip.it/vjBF7> [image: rss feed icon]
> <https://www.pingidentity.com/blogs/>
>
>


-- 
[image: Ping Identity logo] <https://www.pingidentity.com/>
Brian Campbell
Distinguished Engineer
Ping Identity
@ bcampbell@pingidentity.com [image: phone] +1 720.317.2061 [image: twitter]
@pingidentity Connect with us!
<https://www.pingidentity.com/>[image: pingidentity.com]
<https://www.pingidentity.com/>
<https://ping.force.com/Support/PingIdentityCommunityHome>[image:
pingidentity.com] <https://ping.force.com/Support/PingIdentityCommunityHome>
[image: twitter logo]
<http://www.glassdoor.com/Overview/Working-at-Ping-Identity-EI_IE380907.11,24.htm>
[image:
twitter logo] <https://twitter.com/pingidentity> [image: youtube logo]
<https://www.youtube.com/user/PingIdentityTV> [image: LinkedIn logo]
<https://www.linkedin.com/company/21870> [image: Facebook logo]
<https://www.facebook.com/pingidentitypage> [image: Google+ logo]
<https://plus.google.com/u/0/114266977739397708540> [image: slideshare logo]
<http://www.slideshare.net/PingIdentity> [image: flipboard logo]
<http://flip.it/vjBF7> [image: rss feed icon]
<https://www.pingidentity.com/blogs/>