Re: [OAUTH-WG] OAuth PoP Implementation

Roland Hedberg <roland.hedberg@umu.se> Sun, 07 February 2016 08:28 UTC

Return-Path: <roland.hedberg@umu.se>
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 A1D961B3743 for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2016 00:28:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level:
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 p90LKB9NM7Gr for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2016 00:28:15 -0800 (PST)
Received: from smtp5.umu.se (smtp5.umu.se [130.239.8.142]) by ietfa.amsl.com (Postfix) with ESMTP id 29DB81B3746 for <oauth@ietf.org>; Sun, 7 Feb 2016 00:28:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,409,1449529200"; d="asc'?scan'208";a="86272248"
X-IPAS-Result: A2CBBgBq/7ZW/8oN74JeDgsBAQEBDwEBAQGCX31tBohVqWeFDIQHIYVsAoFqAQEBAQEBgQuEQgEBBCNWEAIBCA40AgIyJQIEDhOIDQEDCq8bjj4BAQEBAQEBAwEBAQEBAQEBAQ8EBIYSgW2CSoJUhF4rgQ8FlnWCfoFkaolfh2mFL1yNYmKDKTtqh1cBewEBAQ
Received: from umu-ex02.ad.umu.se (HELO mail.ad.umu.se) ([130.239.13.202]) by smtp5.umu.se with ESMTP; 07 Feb 2016 09:28:11 +0100
Received: from UMU-EX03.ad.umu.se (2002:82ef:dcb::82ef:dcb) by UMU-EX02.ad.umu.se (2002:82ef:dca::82ef:dca) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Sun, 7 Feb 2016 09:27:53 +0100
Received: from UMU-EX03.ad.umu.se ([fe80::708f:f02f:c850:d133]) by UMU-EX03.ad.umu.se ([fe80::708f:f02f:c850:d133%24]) with mapi id 15.00.1130.005; Sun, 7 Feb 2016 09:27:54 +0100
From: Roland Hedberg <roland.hedberg@umu.se>
To: Justin Richer <jricher@MIT.EDU>
Thread-Topic: [OAUTH-WG] OAuth PoP Implementation
Thread-Index: AQHRYYFwBC5SWZiYSEaYM0UW9uL0Qg==
Date: Sun, 7 Feb 2016 08:27:53 +0000
Message-ID: <C33F4294-BB62-486F-A830-0874A94A6EA3@adm.umu.se>
References: <467A26CD-FC42-4E96-AE30-6E4E3B013F41@mit.edu> <CF8F3300-1495-444D-9C22-69E6B70E790E@wahlstromstekniska.se> <56B35E81.2020406@mit.edu>
In-Reply-To: <56B35E81.2020406@mit.edu>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-pgp-agent: GPGMail 2.5.2
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [31.208.6.237]
Content-Type: multipart/signed; boundary="Apple-Mail=_92D996AE-7529-497B-9062-463CBAB1A166"; protocol="application/pgp-signature"; micalg=pgp-sha256
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/DrwEGdZKTj9aWdSOTjUGnL7o99c>
Cc: "<oauth@ietf.org>" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth PoP Implementation
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: Sun, 07 Feb 2016 08:28:17 -0000

So, I’ve done the ’client creates key pair’ version instead :-/

For those who can read and understand Python you can find me implementation attempt on github as an
extension to my oauth2/oidc implementation (https://github.com/rohe/pyoidc).

You can look at the necessary support methods in:

https://github.com/rohe/pyoidc/blob/master/src/oic/extension/pop.py

and a test with some documentation in:

https://github.com/rohe/pyoidc/blob/master/tests/test_pop.py

Should be fairly easy to do the ’AS creates the key pair’ variant.

— Roland