IETF Logo Mail Archive

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

Brian Eaton <beaton@google.com> Thu, 13 May 2010 15:50 UTC

Return-Path: <beaton@google.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 839063A6B90 for <oauth@core3.amsl.com>; Thu, 13 May 2010 08:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.755
X-Spam-Level:
X-Spam-Status: No, score=-105.755 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 2OUGZo3o5IFw for <oauth@core3.amsl.com>; Thu, 13 May 2010 08:50:35 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 830D53A68E1 for <oauth@ietf.org>; Thu, 13 May 2010 08:50:34 -0700 (PDT)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id o4DFoOtu000399 for <oauth@ietf.org>; Thu, 13 May 2010 08:50:24 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273765824; bh=W9KMaQnjw6VgIrlE25G8t729KXA=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=JP5Ixsn6+yje4EB2UbRwwhfKtVE40F6OBlmTodQFL+uOGj5ZaoUsVwU1TKTavMb7W L7ipxUipNx31GTEUkRiKw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=BuUyYU5+k0tiDOiNrhIcknqO1GQS7Yz6ZghXn/GoCMIt3+mreTgDnlB+ZCoFt8kDZ szezazSt8NPkGYXIK2S9g==
Received: from pvc22 (pvc22.prod.google.com [10.241.209.150]) by wpaz24.hot.corp.google.com with ESMTP id o4DFoMtp006472 for <oauth@ietf.org>; Thu, 13 May 2010 08:50:23 -0700
Received: by pvc22 with SMTP id 22so1048904pvc.37 for <oauth@ietf.org>; Thu, 13 May 2010 08:50:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.196.15 with SMTP id t15mr6510799wff.238.1273765822481; Thu, 13 May 2010 08:50:22 -0700 (PDT)
Received: by 10.143.136.7 with HTTP; Thu, 13 May 2010 08:50:22 -0700 (PDT)
In-Reply-To: <C811682C.563A%cmortimore@salesforce.com>
References: <4BEBD694.3090800@lodderstedt.net> <C811682C.563A%cmortimore@salesforce.com>
Date: Thu, 13 May 2010 08:50:22 -0700
Message-ID: <AANLkTimYJ3TqH9swKm4B9DOiHoHjc6QCx9AJbwxXsGIZ@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
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 15:50:36 -0000

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

v2.23.0 | Report a Bug | By Email