IETF Logo Mail Archive

Re: [OAUTH-WG] User and Client identity in the Assertion Flow

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 13 May 2010 16:02 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 1FBC53A68B3 for <oauth@core3.amsl.com>; Thu, 13 May 2010 09:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level:
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.181, 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 K7HEVyJc4yj0 for <oauth@core3.amsl.com>; Thu, 13 May 2010 09:02:19 -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 80BA43A6B12 for <oauth@ietf.org>; Thu, 13 May 2010 09:02:11 -0700 (PDT)
Received: (qmail 30314 invoked from network); 13 May 2010 16:02:01 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 13 May 2010 16:02:01 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Thu, 13 May 2010 09:01:55 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Date: Thu, 13 May 2010 09:02:09 -0700
Thread-Topic: [OAUTH-WG] User and Client identity in the Assertion Flow
Thread-Index: AcrytAQPy1v3fy9uT1e2XqKmkm66jwAAZhEw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3AB478CC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <4BEBD694.3090800@lodderstedt.net> <C811682C.563A%cmortimore@salesforce.com> <AANLkTimYJ3TqH9swKm4B9DOiHoHjc6QCx9AJbwxXsGIZ@mail.gmail.com>
In-Reply-To: <AANLkTimYJ3TqH9swKm4B9DOiHoHjc6QCx9AJbwxXsGIZ@mail.gmail.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] User and Client identity in the Assertion Flow
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: Thu, 13 May 2010 16:02:20 -0000

Will be added to -05.

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Brian Eaton
> Sent: Thursday, May 13, 2010 8:50 AM
> To: Chuck Mortimore
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] User and Client identity in the Assertion Flow
> 
> On Thu, May 13, 2010 at 8:26 AM, Chuck Mortimore
> <cmortimore@salesforce.com> wrote:
> > Our plan is to treat SAML assertions passed over the assertion flow as
> > bearer assertions, so I believe we have everything we need contained
> > within the assertion (issuer + audience + signature).  That being
> > said, if we want this to be an extensible flow, not all assertion
> > formats will be so transparent.
> >
> > I think this is a reasonable suggestion, as long as the
> > clientid/secret are entirely optional.    Not in support of a second User
> Assertion Flow.
> 
> Yes.  This sounds right to me.
> 
> Cheers,
> Brian
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email