Re: [OAUTH-WG] SAML profile comments/questions from the SAML people
Thomas Hardjono <hardjono@MIT.EDU> Thu, 19 August 2010 19:51 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 C52283A6900 for <oauth@core3.amsl.com>; Thu, 19 Aug 2010 12:51:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.18
X-Spam-Level:
X-Spam-Status: No, score=-4.18 tagged_above=-999 required=5 tests=[AWL=-1.582, 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 lCi-HvxeuEhp for <oauth@core3.amsl.com>; Thu, 19 Aug 2010 12:51:32 -0700 (PDT)
Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by core3.amsl.com (Postfix) with ESMTP id 702153A698B for <oauth@ietf.org>; Thu, 19 Aug 2010 12:51:32 -0700 (PDT)
X-AuditID: 12074423-b7b19ae0000059ef-e3-4c6d8b579c12
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-6.mit.edu (Symantec Brightmail Gateway) with SMTP id D8.24.23023.75B8D6C4; Thu, 19 Aug 2010 15:51:51 -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 o7JJq6Fq021219; Thu, 19 Aug 2010 15:52:06 -0400
Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) ) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id o7JJq6xa008845; Thu, 19 Aug 2010 15:52:06 -0400
Received: from oc11exhub4.exchange.mit.edu (18.9.3.14) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 19 Aug 2010 15:51:38 -0400
Received: from EXPO10.exchange.mit.edu ([18.9.4.15]) by oc11exhub4.exchange.mit.edu ([18.9.3.14]) with mapi; Thu, 19 Aug 2010 15:52:05 -0400
From: Thomas Hardjono <hardjono@MIT.EDU>
To: Brian Campbell <bcampbell@pingidentity.com>, oauth <oauth@ietf.org>
Date: Thu, 19 Aug 2010 15:52:04 -0400
Thread-Topic: [OAUTH-WG] SAML profile comments/questions from the SAML people
Thread-Index: Acs34EEn4vNeZz+NRby6lt941qsNXQH9qdJw
Message-ID: <DADD7EAD88AB484D8CCC328D40214CCD01BFFBF61D@EXPO10.exchange.mit.edu>
References: <AANLkTim7qdDm45N7D-7Zoo9Ew3g1ibQg7CWoUzX+ds61@mail.gmail.com>
In-Reply-To: <AANLkTim7qdDm45N7D-7Zoo9Ew3g1ibQg7CWoUzX+ds61@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [OAUTH-WG] 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: Thu, 19 Aug 2010 19:51:34 -0000
Again apologies for my late comments. __________________________________________ > -----Original Message----- > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > Of Brian Campbell > Sent: Monday, August 09, 2010 12:30 PM > To: oauth > Subject: [OAUTH-WG] SAML profile comments/questions from the SAML > people > > I received some feedback on the SAML profile from a cross posting on > the OASIS SSTC (SAML) list. Links to the thread topic index are > below[1], if you are interested, but I'll try and summarize the two > primary issues here. > > First, concern was expressed that restricting the assertion to only > allow for a single <SubjectConfirmation> element was too limiting. > The restriction basically limits the ability of a single assertion to > be issued for use across multiple use-cases/profiles. A good example > is the use-case that Prateek recently brought up in a different thread > on this list[2] where the assertion is delivered to an SP via Web SSO > and then that SP uses that same assertion to acquire an access token > for data services at a 3rd party site. As currently written, > draft-campbell-oauth-saml-00[3], wouldn't allow for that use-case. > I'm starting to think that my attempt at simplification was is indeed > too restrictive. Allowing for more than one <SubjectConfirmation> will > make the wording in the profile a bit more complicated (as well as > implementing validation) but I think, in the longer term, it's probably > the right thing to do from a spec perspective. At this point I'm > planning on loosening that restriction in the next draft. I'm curious, > however, if anyone has any strong opinions on it one way or the other? I was under the impression that the Oauth use-case was intentionally made to be simple, where the client talks direct to the Authorization Server (not via Web-SSO and the SP, as in the classic SAML use-case). Does Oauth-v2 today allow the Authorization Server to delegate/relegate the actual obtaining of the access token to a 3rd Party? > The second issue involves my assumption and requirement in the profile > that the subject of the assertion be the resource owner. To me, it > seemed like a reasonable and useful constraint that was generally > inline with the spirit of the assertion flow, ... I think there are a large number of SAML-based use cases that can be interestingly "layered" atop OAuth. I guess the question is how complex should we get in Oauth-v2. Perhaps for now you should make the subject of the assertion be the resource owner, to be in-line with the basic Oauth design assumptions. /thomas/
- [OAUTH-WG] SAML profile comments/questions from t… Brian Campbell
- Re: [OAUTH-WG] SAML profile comments/questions fr… Chuck Mortimore
- Re: [OAUTH-WG] SAML profile comments/questions fr… Brian Campbell
- Re: [OAUTH-WG] SAML profile comments/questions fr… Thomas Hardjono
- Re: [OAUTH-WG] SAML profile comments/questions fr… Brian Campbell
- Re: [OAUTH-WG] SAML profile comments/questions fr… Thomas Hardjono
- Re: [OAUTH-WG] SAML profile comments/questions fr… Brian Campbell