Re: [OAUTH-WG] [Ace] Questions about OAuth and DTLS

Ludwig Seitz <ludwig@sics.se> Mon, 08 February 2016 07:50 UTC

Return-Path: <ludwig@sics.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 828741ACD19 for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2016 23:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=unavailable
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 bdv8iIEP-kMl for <oauth@ietfa.amsl.com>; Sun, 7 Feb 2016 23:50:13 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (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 81CCA1ACD12 for <oauth@ietf.org>; Sun, 7 Feb 2016 23:50:12 -0800 (PST)
Received: by mail-lb0-x22f.google.com with SMTP id dx2so78202994lbd.3 for <oauth@ietf.org>; Sun, 07 Feb 2016 23:50:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sics-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=wzwEM3BOnfR+swR4gC0AFKZOkjilschzMJuFUFWrSd8=; b=DN4aI1IftK+jb8nOCf5VV06LLwZTsdx/rvdkLaZiy3KBUCYUSIxyeo/d/weXNFGE8F DWkx7iegmdLxgOtIEdCGQip9L/Nwg0DmQV16JpASJHx6RZXlPltn7CwQ4Ac3LOd2xLWx a9dPOqJDk1OY2+eidfWZ6fTHYbb1HuWQTGyN6d+mJm+vQxAsjYO2Th+yh64Oe9eIfK66 6mGhosD/XuVKimP26K9EOIUDaswYfWxy8RCxSgzAqXIXaR+4dAH05drqJm/2I+ufQB2t SKMIr4ewAqp73zdkNXGJ6wZnf5kBCJUGXTYXKzoExnbji+zWRzH4P/Lt7Tbuf2Z+XFBG RcCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=wzwEM3BOnfR+swR4gC0AFKZOkjilschzMJuFUFWrSd8=; b=d0G7hpNOucwbNRPKK8WMtsOmH9uh9OeZ7lfPKoDBHxwNnQPe9SHo1O78OLi/bkxWMk zyraAdrVpAzik7gfQSRJu8dy1LMQSrEDbDnEb3apK0iJBRYw9nGt6gbaeEoM85u05Ztp YgSqiNFYGjGsj/bDGkm8Mb2Q1RZQlSpnlYswbl9Tizo+UvrUfo+9iNlvBLzIXztL2+Mu 9Naunx2c690d8UWgXb8hjXoEeDRJGALa3HUgTwn6IIXqHO+EAwDs82GbaADBK1VpogZT OGxy5PGNDqAeLmI/gkS1jAaoJgiQeDP8rHNeywtEIQs4bNzJitpSY8JhjqSGh5vGyUkg t1OQ==
X-Gm-Message-State: AG10YOSS2vPZg/Y+bye7pw8+wI/QmdB71pwjrRR4tPgQSfNdlWOx+Q9CRCOOncpFt1TIFtJA
X-Received: by 10.112.25.99 with SMTP id b3mr3633382lbg.11.1454917810668; Sun, 07 Feb 2016 23:50:10 -0800 (PST)
Received: from Hyperion.suse ([85.235.10.186]) by smtp.gmail.com with ESMTPSA id ke9sm3716915lbc.28.2016.02.07.23.50.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Feb 2016 23:50:10 -0800 (PST)
To: Samuel Erdtman <samuel@erdtman.se>
References: <56B31FEB.4010204@sics.se> <CAF2hCbaiJLWihcgNV7B=1Kzq8WZGRd8wSF0UeD=uF8vhck-g3g@mail.gmail.com>
From: Ludwig Seitz <ludwig@sics.se>
Message-ID: <56B848A0.20503@sics.se>
Date: Mon, 8 Feb 2016 08:49:52 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <CAF2hCbaiJLWihcgNV7B=1Kzq8WZGRd8wSF0UeD=uF8vhck-g3g@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms000605080601030200040006"
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/cEmg_iJYouHro6xwDRyfXeWjCiI>
Cc: oauth@ietf.org, ace@ietf.org
Subject: Re: [OAUTH-WG] [Ace] Questions about OAuth and DTLS
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: Mon, 08 Feb 2016 07:50:15 -0000

On 02/07/2016 06:24 PM, Samuel Erdtman wrote:
> Hi,
>
~snip~
> But I think there is some compelling properties of having a symmetric
> PoP key and a Raw Public Key (D)TLS. In this case the Public key of the
> RS can be distributed to the client in the client information (the
> attributes accompanying the token) from AS and the PoP key as defined by
> PoP key distribution draft. With this setup the client can authenticate
> the server at connection time and then it can send its PoP token to
> authorization information endpoint/resource at the RS (defined in
> draft-ietf-ace-oauth-authz as an alternative to the HTTP Authorization
> header) to authorize the client.
>

In this case you need to perform an additional proof-of-possession step. 
Worse, we have to define a new protocol for this.

@OAuth: It is not really clear to me from reading the PoP drafts, what 
the acceptable proof-of-possession methods are. Is this some work that 
the WG is planning to do?

/Ludwig



-- 
Ludwig Seitz, PhD
SICS Swedish ICT AB
Ideon Science Park
Building Beta 2
Scheelevägen 17
SE-223 70 Lund

Phone +46(0)70 349 9251
http://www.sics.se