IETF Logo Mail Archive

Re: [OAUTH-WG] Delegation -- RE: SAML profile comments/questions from the SAML people

Thomas Hardjono <hardjono@MIT.EDU> Tue, 14 September 2010 17:33 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 A744A3A6AC6 for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 10:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.304
X-Spam-Level:
X-Spam-Status: No, score=-3.304 tagged_above=-999 required=5 tests=[AWL=-1.306, BAYES_00=-2.599, J_CHICKENPOX_61=0.6, 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 ASYHGaymzZcL for <oauth@core3.amsl.com>; Tue, 14 Sep 2010 10:32:57 -0700 (PDT)
Received: from dmz-mailsec-scanner-5.mit.edu (DMZ-MAILSEC-SCANNER-5.MIT.EDU [18.7.68.34]) by core3.amsl.com (Postfix) with ESMTP id DB69D3A6A00 for <oauth@ietf.org>; Tue, 14 Sep 2010 10:32:53 -0700 (PDT)
X-AuditID: 12074422-b7bbfae000005e9b-06-4c8fb1cbe99c
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-5.mit.edu (Symantec Brightmail Gateway) with SMTP id 84.24.24219.BC1BF8C4; Tue, 14 Sep 2010 13:32:59 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id o8EHX8Jp023967; Tue, 14 Sep 2010 13:33:08 -0400
Received: from oc11exedge1.exchange.mit.edu (OC11EXEDGE1.EXCHANGE.MIT.EDU [18.9.3.17]) ) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id o8EHX7SC004649; Tue, 14 Sep 2010 13:33:07 -0400
Received: from oc11exhub4.exchange.mit.edu (18.9.3.14) by oc11exedge1.exchange.mit.edu (18.9.3.17) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 14 Sep 2010 13:32:48 -0400
Received: from EXPO10.exchange.mit.edu ([18.9.4.15]) by oc11exhub4.exchange.mit.edu ([18.9.3.14]) with mapi; Tue, 14 Sep 2010 13:33:07 -0400
From: Thomas Hardjono <hardjono@MIT.EDU>
To: "Zeltsan, Zachary (Zachary)" <zachary.zeltsan@alcatel-lucent.com>, "Faynberg, Igor (Igor)" <igor.faynberg@alcatel-lucent.com>
Date: Tue, 14 Sep 2010 13:33:04 -0400
Thread-Topic: [OAUTH-WG] Delegation -- RE: SAML profile comments/questions from the SAML people
Thread-Index: ActOzGFQvhoQfZOXQCaYovoauidPGQAAxeYgAFh1YXAA71lAQAAQ+9/A
Message-ID: <DADD7EAD88AB484D8CCC328D40214CCD01C353D441@EXPO10.exchange.mit.edu>
References: <DADD7EAD88AB484D8CCC328D40214CCD01C253AA42@EXPO10.exchange.mit.edu> <4C86A248.20501@alcatel-lucent.com> <5710F82C0E73B04FA559560098BF95B124FB2333D2@USNAVSXCHMBSA3.ndc.alcatel-lucent.com> <DADD7EAD88AB484D8CCC328D40214CCD01C2BC5FC8@EXPO10.exchange.mit.edu> <5710F82C0E73B04FA559560098BF95B124FB2333DB@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <5710F82C0E73B04FA559560098BF95B124FB2333DB@USNAVSXCHMBSA3.ndc.alcatel-lucent.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 <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Delegation -- RE: SAML profile comments/questions from the SAML people
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, 14 Sep 2010 17:33:01 -0000

Thanks Zachary,

> -----Original Message-----
> From: Zeltsan, Zachary (Zachary) [mailto:zachary.zeltsan@alcatel-
> lucent.com]
> Sent: Tuesday, September 14, 2010 6:24 AM
> To: Thomas Hardjono; Faynberg, Igor (Igor)
> Cc: oauth
> Subject: RE: [OAUTH-WG] Delegation -- RE: SAML profile
> comments/questions from the SAML people
> 
> Thomas,
> 
> The draft does not specify a limit on the number of delegations from
> Client#N to Client#(N+1).

ok, great.
> 
> The draft's revision would require a substantial work because the draft
> relies on the community version of OAuth, which differs significantly
> from the current OAuth v.2. I am talking with our developers to
> determine if there is sufficient support for this work.

Hmm, I guess it is always a good thing to have code as close as possible to spec :) 

/thomas/


> 
> Zachary
> -----Original Message-----
> From: Thomas Hardjono [mailto:hardjono@mit.edu]
> Sent: Thursday, September 09, 2010 11:13 AM
> To: Zeltsan, Zachary (Zachary); Faynberg, Igor (Igor)
> Cc: oauth
> Subject: RE: [OAUTH-WG] Delegation -- RE: SAML profile
> comments/questions from the SAML people
> 
> 
> Thanks Igor and Zachary,
> 
> Are there any plans to renew this expired draft?  Also, is there a
> limitation to the number of "swaps" that can be supported?
> 
> Thanks.
> 
> /thomas/
> 
> __________________________________________
> 
> > -----Original Message-----
> > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On
> Behalf
> > Of Zeltsan, Zachary (Zachary)
> > Sent: Tuesday, September 07, 2010 5:15 PM
> > To: Faynberg, Igor (Igor); Thomas Hardjono
> > Cc: oauth
> > Subject: Re: [OAUTH-WG] Delegation -- RE: SAML profile
> > comments/questions from the SAML people
> >
> > Igor,
> >
> > The intention of the draft draft-vrancken-oauth-redelegation was to
> > specify a mechanism for doing exactly what Thomas has described:
> > > ... User#1/Client#1 asks for
> > > an access token (to a given resource) with the intention of later
> > > handing over the access-token to a different User#2/Client#2
> > The mechanism is design to support also the situation where
> > > User#2/Client#2 asks the Auth Server to "swap" (re-issue) this
> token
> > > for a different client_id (User#3/Client#3)
> >
> > The difference is that the mechanism of the draft-vrancken-oauth-
> > redelegation relies on the "temporary credentials" and "token
> > credentials", which were used in OAuth 1.0, and not on the access
> > tokens.
> >
> > Zachary
> > -----Original Message-----
> > From: Igor Faynberg [mailto:igor.faynberg@alcatel-lucent.com]
> > Sent: Tuesday, September 07, 2010 4:36 PM
> > To: Thomas Hardjono; Zeltsan, Zachary (Zachary)
> > Cc: Brian Campbell; oauth
> > Subject: Re: [OAUTH-WG] Delegation -- RE: SAML profile
> > comments/questions from the SAML people
> >
> > Thomas,
> >
> > It looks to me like the intention in this use case is similar to that
> > of the "multilegged OAuth" (later renamed to the politically-correct
> > "recursive delegation"). This use case has been published in Bart's
> and
> > Zachary's draft. which has expired now. This case has moved into the
> > overall use case compilation document.
> >
> > Zachary, maybe you could shed some light here?
> >
> > Igor
> >
> > Thomas Hardjono wrote:
> > > __________________________________________
> > >
> > >
> > >> -...
> > >
> > > What I meant to say is that User#1/Client#1 asks for an access
> token
> > > (to a given resource) with the intention of later handing over the
> > > access-token to a different User#2/Client#2.
> > >
> > > Ideally, this model could be extensible where
> > > User#2/Client#2 asks the Auth Server to "swap" (re-issue) this
> token
> > > for a different client_id (User#3/Client#3).
> > >
> > > However, this bring us into space of role based access control and
> > > permissions, which would somewhat complicate the Oauth 2.0
> > > authorization model :)
> > >
> > > /thomas/
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > 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