IETF Logo Mail Archive

Re: [OAUTH-WG] Assertion flow and token bootstrapping

Thomas Hardjono <hardjono@MIT.EDU> Mon, 07 June 2010 17:20 UTC

Return-Path: <hardjono@mit.edu>
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 1D2453A6DE9 for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 10:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.299, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 zOQSZbZt7qSe for <oauth@core3.amsl.com>; Mon, 7 Jun 2010 10:20:55 -0700 (PDT)
Received: from dmz-mailsec-scanner-1.mit.edu (DMZ-MAILSEC-SCANNER-1.MIT.EDU [18.9.25.12]) by core3.amsl.com (Postfix) with ESMTP id E9A2628C528 for <oauth@ietf.org>; Mon, 7 Jun 2010 08:48:00 -0700 (PDT)
X-AuditID: 1209190c-b7bd2ae000005d05-4a-4c0d030ed562
Received: from mailhub-auth-4.mit.edu (MAILHUB-AUTH-4.MIT.EDU [18.7.62.39]) by dmz-mailsec-scanner-1.mit.edu (Symantec Brightmail Gateway) with SMTP id 7C.3D.23813.E030D0C4; Mon, 7 Jun 2010 10:32:46 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-EXCHANGE-2.MIT.EDU [18.9.28.16]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id o57EWkDp028954; Mon, 7 Jun 2010 10:32:46 -0400
Received: from w92exedge3.EXCHANGE.MIT.EDU (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) ) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id o57EWgu7010878; Mon, 7 Jun 2010 10:32:46 -0400
Received: from oc11exhub1.exchange.mit.edu (18.9.3.11) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 8.1.393.1; Mon, 7 Jun 2010 10:32:13 -0400
Received: from EXPO10.exchange.mit.edu ([18.9.4.15]) by oc11exhub1.exchange.mit.edu ([18.9.3.11]) with mapi; Mon, 7 Jun 2010 10:32:42 -0400
From: Thomas Hardjono <hardjono@MIT.EDU>
To: Dick Hardt <dick.hardt@gmail.com>
Date: Mon, 07 Jun 2010 10:32:40 -0400
Thread-Topic: [OAUTH-WG] Assertion flow and token bootstrapping
Thread-Index: AcsF1f/j29sX9+E2SBa/6rmqqrl8FAAd9GKQ
Message-ID: <DADD7EAD88AB484D8CCC328D40214CCD0179258E2E@EXPO10.exchange.mit.edu>
References: <AANLkTilYX46pz5qI67nrgYxB_Lf1tx8DZM9YYs-QuT9T@mail.gmail.com> <DADD7EAD88AB484D8CCC328D40214CCD0179258AC0@EXPO10.exchange.mit.edu> <AANLkTimc8tUKxMmm6yCk2Nd_sRQpd8nJbBUgOhUi9EIh@mail.gmail.com> <AANLkTilkKlU71vA5Gm5kwmbgsTsDmtw8xQfq_HrtgyrV@mail.gmail.com> <DADD7EAD88AB484D8CCC328D40214CCD0179258BA5@EXPO10.exchange.mit.edu> <4C07C84C.9070705@stpeter.im> <AANLkTimsii6OMCXzyeQczM-Yq9CB3klJweTQ_TL9P9qp@mail.gmail.com> <700AC043-9E28-491D-B3CD-789245E30EA9@pingidentity.com> <57FA7F56-ADC2-404A-950E-5D43FBDE75D9@facebook.com> <4C2E55D5-072B-4F08-A341-7405F2F1C944@gmail.com> <DADD7EAD88AB484D8CCC328D40214CCD0179258DC5@EXPO10.exchange.mit.edu> <77E0A4F9-9211-4E2A-B6A1-4E812192BA82@gmail.com>
In-Reply-To: <77E0A4F9-9211-4E2A-B6A1-4E812192BA82@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Assertion flow and token bootstrapping
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: Mon, 07 Jun 2010 17:20:56 -0000

Thanks Dick.  I was just kinda confused: if the Assertion Flow was already in the WRAP draft and now in the core spec (OAuth2.0-draft-05), what do we gain from separating it off again.

/thomas/

__________________________________________


> -----Original Message-----
> From: Dick Hardt [mailto:dick.hardt@gmail.com]
> Sent: Sunday, June 06, 2010 8:10 PM
> To: Thomas Hardjono
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] Assertion flow and token bootstrapping
> 
> I hope so.
> 
> On 2010-06-06, at 3:22 PM, Thomas Hardjono wrote:
> 
> > Apologies for another newbie question: is the design-intention underlying
> the Assertion Flow in OAuth2.0-draft-05 the same as that in the WRAP draft
> (draft-hardt-oauth-01)?
> >
> > /thomas/
> >
> > __________________________________________
> >
> >> -----Original Message-----
> >> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of
> >> Dick Hardt
> >> Sent: Friday, June 04, 2010 9:59 PM
> >> To: Luke Shepard
> >> Cc: oauth@ietf.org
> >> Subject: Re: [OAUTH-WG] Assertion flow and token bootstrapping
> >>
> >> because we use it
> >>
> >> On 2010-06-04, at 6:40 PM, Luke Shepard wrote:
> >>
> >>> Why?
> >>>
> >>> On Jun 4, 2010, at 4:41 PM, Patrick Harding wrote:
> >>>
> >>>> +1
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>> On Jun 4, 2010, at 5:38 PM, Brian Campbell
> >>>> <bcampbell@pingidentity.com> wrote:
> >>>>
> >>>>> On Thu, Jun 3, 2010 at 9:20 AM, Peter Saint-Andre
> >>>>> <stpeter@stpeter.im> wrote:
> >>>>>>
> >>>>>> At least for the assertion flow, that's definitely true. At the
> >>>>>> interim
> >>>>>> meeting we had some discussion about perhaps pulling the assertion
> >>>>>> flow
> >>>>>> out of the base spec and into a separate document. Perhaps that's the
> >>>>>> best way to proceed.
> >>>>>
> >>>>>
> >>>>> I'd like to see the assertion flow remain in the base spec.
> >>>>> _______________________________________________
> >>>>> 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
> >>
> >> _______________________________________________
> >> OAuth mailing list
> >> OAuth@ietf.org
> >> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email