Re: [OAUTH-WG] OAuth Security Discussions

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 17 September 2012 16:21 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD6421F8705 for <oauth@ietfa.amsl.com>; Mon, 17 Sep 2012 09:21:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.823
X-Spam-Level:
X-Spam-Status: No, score=-101.823 tagged_above=-999 required=5 tests=[AWL=-0.224, BAYES_00=-2.599, J_BACKHAIR_22=1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dieTaUW5WNTm for <oauth@ietfa.amsl.com>; Mon, 17 Sep 2012 09:21:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 55B1E21F86E1 for <oauth@ietf.org>; Mon, 17 Sep 2012 09:21:51 -0700 (PDT)
Received: (qmail invoked by alias); 17 Sep 2012 16:21:48 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.216.191] by mail.gmx.net (mp035) with SMTP; 17 Sep 2012 18:21:48 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/GfQlKq/HGtUhoAk74qhM8YRb52z64v0bFVlIQdP +9ydQvs4z1JGMR
Message-ID: <50574E12.6060400@gmx.net>
Date: Mon, 17 Sep 2012 19:21:38 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Justin Richer <jricher@mitre.org>
References: <OF6192366F.9DD38E70-ON48257A76.0011F223-48257A76.001221CB@zte.com.cn> <5057136C.6070600@gmx.net> <50573008.7090200@mitre.org>
In-Reply-To: <50573008.7090200@mitre.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: oauth-bounces@ietf.org, "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth Security Discussions
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 17 Sep 2012 16:21:52 -0000

Good point, Justin.  I was thinking a bit too narrowly here.

On 09/17/2012 05:13 PM, Justin Richer wrote:
> On 09/17/2012 08:11 AM, Hannes Tschofenig wrote:
>>> Since it is prefered to have long lived key shared between AS and RS in
>>> this WG,
>>> Is there any consideration for this key distribution and its security
>>> requirements?
>> So far we have had only discussions regarding the standardization of the
>> AS<->RS server interaction in the context of the UMA work.
>>
>> You may want to have a look at
>> http://tools.ietf.org/html/draft-hardjono-oauth-umacore
>>
> Not quite true. There's also the token introspection, like Ping has
> published[1] or what AOL or MITRE have both implemented. You also have
> to account for those using structured tokens (like JWTs) with signatures
> to communicate using the token itself, analogous to SAML assertions.
>
> When we brought it up during the re-chartering discussion, there seemed
> to be a number of folks willing to work on publishing something in this
> area.
>
>   -- Justin
>
> [1] http://www.ietf.org/mail-archive/web/oauth/current/msg08607.html