Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"

Eran Hammer <eran@hueniverse.com> Sun, 11 March 2012 15:57 UTC

Return-Path: <eran@hueniverse.com>
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 9ADC521F86E5 for <oauth@ietfa.amsl.com>; Sun, 11 Mar 2012 08:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6rsEm-UZ1w0 for <oauth@ietfa.amsl.com>; Sun, 11 Mar 2012 08:57:24 -0700 (PDT)
Received: from p3plex2out01.prod.phx3.secureserver.net (p3plex2out01.prod.phx3.secureserver.net [184.168.131.12]) by ietfa.amsl.com (Postfix) with ESMTP id 2349521F84E7 for <oauth@ietf.org>; Sun, 11 Mar 2012 08:57:24 -0700 (PDT)
Received: from P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.46]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id kFxP1i00610TkE001FxP5t; Sun, 11 Mar 2012 08:57:23 -0700
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT004.EX1.SECURESERVER.NET ([72.167.180.134]) with mapi; Sun, 11 Mar 2012 08:57:23 -0700
From: Eran Hammer <eran@hueniverse.com>
To: nov matake <nov@matake.jp>, "oauth@ietf.org WG" <oauth@ietf.org>
Date: Sun, 11 Mar 2012 08:57:22 -0700
Thread-Topic: [OAUTH-WG] Clarification of "client application consisting of multiple components"
Thread-Index: Acz/mzWcUPpRJfNDR66NHAA/GYvcvgABFasw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AFF08605@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <62D85564-7961-4AB6-B1FA-B2DD75A4C74B@matake.jp>
In-Reply-To: <62D85564-7961-4AB6-B1FA-B2DD75A4C74B@matake.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Clarification of "client application consisting of multiple components"
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: Sun, 11 Mar 2012 15:57:24 -0000

If you have two components each with different security profile, you must assign each a different client_id. Otherwise, there is no way to enforce the rest of the spec's security requirements.

EH

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of nov matake
> Sent: Sunday, March 11, 2012 8:25 AM
> To: oauth@ietf.org WG
> Subject: [OAUTH-WG] Clarification of "client application consisting of multiple
> components"
> 
> Hi,
> 
> I just found this sentence in the latest draft.
> 
> Does it mean "an application consisting of server-side and client-side
> component (eg. foursquare iPhone app) MUST have separate client_id for
> each component" ?
> Or can I image something like Facebook is doing right now? (register each
> component for a single client_id separately)
> 
> ==
> A client application consisting of multiple components, each with its own
> client type (e.g. a distributed client with both a confidential server-based
> component and a public browser-based component), MUST register each
> component separately as a different client to ensure proper handling by the
> authorization server.  The authorization server MAY provider tools to manage
> such complex clients through a single administration interface.
> ==
> 
> --
> nov <nov@matake.jp>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth