IETF Logo Mail Archive

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

Torsten Lodderstedt <torsten@lodderstedt.net> Thu, 13 May 2010 16:12 UTC

Return-Path: <torsten@lodderstedt.net>
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 14BA53A6B12 for <oauth@core3.amsl.com>; Thu, 13 May 2010 09:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[AWL=0.618, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 PEtU9crkjuvc for <oauth@core3.amsl.com>; Thu, 13 May 2010 09:12:15 -0700 (PDT)
Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.29.23]) by core3.amsl.com (Postfix) with ESMTP id 0D97D3A6B27 for <oauth@ietf.org>; Thu, 13 May 2010 09:12:14 -0700 (PDT)
Received: from [79.255.34.226] (helo=[192.168.71.22]) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OCb12-0000gj-2g; Thu, 13 May 2010 18:12:04 +0200
References: <4BEBD694.3090800@lodderstedt.net> <C811682C.563A%cmortimore@salesforce.com> <AANLkTimYJ3TqH9swKm4B9DOiHoHjc6QCx9AJbwxXsGIZ@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343B3AB478CC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Message-Id: <31255129-569C-4D7B-8A9B-5478681A90DF@lodderstedt.net>
From: Torsten Lodderstedt <torsten@lodderstedt.net>
To: Eran Hammer-Lahav <eran@hueniverse.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3AB478CC@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
X-Mailer: iPhone Mail (7E18)
Mime-Version: 1.0 (iPhone Mail 7E18)
Date: Thu, 13 May 2010 18:11:43 +0200
X-Df-Sender: 141509
Cc: "oauth@ietf.org" <oauth@ietf.org>
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:12:16 -0000

Thanks.



Am 13.05.2010 um 18:02 schrieb Eran Hammer-Lahav <eran@hueniverse.com>:

> 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
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email