Re: [OAUTH-WG] Proposed language for section 2.2 on Client Assertions

Eran Hammer-Lahav <eran@hueniverse.com> Tue, 10 August 2010 04:45 UTC

Return-Path: <eran@hueniverse.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 974193A68C0 for <oauth@core3.amsl.com>; Mon, 9 Aug 2010 21:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level:
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qawhLlDci-p for <oauth@core3.amsl.com>; Mon, 9 Aug 2010 21:45:46 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 67FC83A6A1E for <oauth@ietf.org>; Mon, 9 Aug 2010 21:45:46 -0700 (PDT)
Received: (qmail 22522 invoked from network); 10 Aug 2010 04:46:21 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 10 Aug 2010 04:46:20 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Mon, 9 Aug 2010 21:46:20 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Yaron Goland <yarong@microsoft.com>, Brian Campbell <bcampbell@pingidentity.com>, oauth <oauth@ietf.org>
Date: Mon, 09 Aug 2010 21:46:25 -0700
Thread-Topic: [OAUTH-WG] Proposed language for section 2.2 on Client Assertions
Thread-Index: AQHLLaFrKvkKC0RiQEq67TG16TjkBJLZtKvggAB91uA=
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3F1243FC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <7C01E631FF4B654FA1E783F1C0265F8C6294F782@TK5EX14MBXC113.redmond.corp.microsoft.com> <90C41DD21FB7C64BB94121FBBC2E72343B3EF900AE@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTi=eSd1nqsNNOUH5x4GznSF+ws5QFmvV0Xq5HxO0@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3EF90102@P3PW5EX1MB01.EX1.SECURESERVER.NET> <AANLkTi=-RB4rDL9u8dXcP5K5g+f9TE1c4U169wTd+NTi@mail.gmail.com> <AANLkTimfe_vs_VUOwvvfR5TCfHa5mjejHqzwVRdXcu4F@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3EF901EC@P3PW5EX1MB01.EX1.SECURESERVER.NET> <7C01E631FF4B654FA1E783F1C0265F8C62A62B83@TK5EX14MBXC115.redmond.corp.microsoft.com>
In-Reply-To: <7C01E631FF4B654FA1E783F1C0265F8C62A62B83@TK5EX14MBXC115.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Proposed language for section 2.2 on Client Assertions
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 10 Aug 2010 04:45:47 -0000

[Seems like the only way is for me to say this]

I am going to include this text in -11 unless someone objects (and explains why).

EHL

> -----Original Message-----
> From: Yaron Goland [mailto:yarong@microsoft.com]
> Sent: Monday, August 09, 2010 2:16 PM
> To: Eran Hammer-Lahav; Brian Campbell; oauth
> Subject: RE: [OAUTH-WG] Proposed language for section 2.2 on Client
> Assertions
> 
> So how do we resolve if the language goes into the spec?
> 	Thanks,
> 		Yaron
> 
> > -----Original Message-----
> > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> > Of Eran Hammer-Lahav
> > Sent: Tuesday, July 27, 2010 8:36 AM
> > To: Brian Campbell; oauth
> > Subject: Re: [OAUTH-WG] Proposed language for section 2.2 on Client
> > Assertions
> >
> > Makes sense. Personally, I don't have any preference on including it or not.
> >
> > EHL
> >
> > > -----Original Message-----
> > > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
> > > Behalf Of Brian Campbell
> > > Sent: Tuesday, July 27, 2010 5:49 AM
> > > To: oauth
> > > Subject: Re: [OAUTH-WG] Proposed language for section 2.2 on Client
> > > Assertions
> > >
> > > A client_id parameter would still be presented in the end user
> > > authorization request. The text Brian E. quoted is what mandates any
> > > specifications/documents/agreements that define how to use client
> > > assertions must also define the association between the client_id
> > > and some
> > > field(s) in the assertion.
> > >
> > > If someone sees a cleaner way to deal with client identity on the
> > > user authorization request when using assertions to authenticate the
> client
> > > to the token endpoint, please speak up and lets discuss it.   However,
> > > in general I do feel it's important to have better defined support
> > > in the core OAuth spec to allow for client authentication methods
> > > beyond just password.
> > >
> > > -Brian
> > >
> > > On Mon, Jul 26, 2010 at 5:18 PM, Brian Eaton <beaton@google.com>
> wrote:
> > > > On Mon, Jul 26, 2010 at 4:11 PM, Eran Hammer-Lahav
> > > <eran@hueniverse.com> wrote:
> > > >> How do you link the client_id using in the authorization endpoint
> > > >> with the
> > > client assertion using in the token endpoint?
> > > >
> > > > In theory:
> > > >
> > > > "any document that defines how to use an assertion of a particular
> > > > type with OAuth 2.0 MUST define how to map the value from the
> > > > client_id parameter in the authorization request to a value or
> > > > values in the assertion subsequently submitted with the code to
> > > > obtain an access token."
> > > >
> > > > In practice: you do it the same way you handle any kind of
> > > > identity assertion.  There is some combination of issuer and
> > > > subject and signature that ends up producing an identity that you trust.
> > > > _______________________________________________
> > > > 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
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth