Re: [OAUTH-WG] more than one assertion?
Eran Hammer-Lahav <eran@hueniverse.com> Tue, 10 August 2010 04:43 UTC
Return-Path: <eran@hueniverse.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 52BF23A6849 for <oauth@core3.amsl.com>; Mon, 9 Aug 2010 21:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level:
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=-0.251, BAYES_00=-2.599, HTTP_ESCAPED_HOST=0.134, J_CHICKENPOX_93=0.6]
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 ZZYAgTzoivCF for <oauth@core3.amsl.com>; Mon, 9 Aug 2010 21:43:17 -0700 (PDT)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id 64DDD3A67B8 for <oauth@ietf.org>; Mon, 9 Aug 2010 21:43:16 -0700 (PDT)
Received: (qmail 4401 invoked from network); 10 Aug 2010 04:43:50 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 10 Aug 2010 04:43:50 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Mon, 9 Aug 2010 21:43:50 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Campbell <bcampbell@pingidentity.com>, oauth <oauth@ietf.org>
Date: Mon, 09 Aug 2010 21:43:55 -0700
Thread-Topic: [OAUTH-WG] more than one assertion?
Thread-Index: Acs3+emsqaTrzVNxTIWVzQDzqoXRaQATJExA
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3F1243FB@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <AANLkTinkTA4uSvUB64u2cdnzmYpxjfTTn43PuB9aMo6M@mail.gmail.com>
In-Reply-To: <AANLkTinkTA4uSvUB64u2cdnzmYpxjfTTn43PuB9aMo6M@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
Subject: Re: [OAUTH-WG] more than one assertion?
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, 10 Aug 2010 04:43:18 -0000
Do we need to clarify 4.3.1 "repeats a parameter" description for "invalid_request" error code does not preclude parameters from repeating? I'm not sure. EHL > -----Original Message----- > From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf > Of Brian Campbell > Sent: Monday, August 09, 2010 12:34 PM > To: oauth > Subject: [OAUTH-WG] more than one assertion? > > The question of allowing for multiple assertions in the SAML profile came up > recently. See http://www.ietf.org/mail- > archive/web/oauth/current/msg04068.html and several subsequent > messages in the thread. > > I pushed back on the idea at first due to added complexity. There are a > number of things that need to be addressed that aren't present in > the single assertion case. One of the sticker ones, to me, was how > to encode the assertions into the request. A SAML <Response> element > is a nice container for multiple assertions but using it in this context seemed > awkward at best. A new schema could be defined or a special deliminator > character could be used but that seems excessive and kludgy respectively. > > What about pushing it up into the HTTP layer and allowing for multiple > occurrences of the assertion=XXX parameter in the POST body? I don't see > anything in core OAuth that would necessarily preclude doing this. > It seems cleaner and more lightweight than some of the other options. > And perhaps it could be a more general (not just SAML) method of sending > multiple assertions in a single assertion grant type request? > > It'd look something like this: > > POST /token.oauth2 HTTP/1.1 > Host: authz.example.net > Content-Type: application/x-www-form-urlencoded > > grant_type=assertion&assertion_type=http%3A%2F%2Foauth.net%2Fasse > rtion_type%2Fsaml%2F2.0%2Fbearer&assertion=[...1st > assertion...]&assertion= > [...2nd assertion...]&assertion=[...3nd assertion...] > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] more than one assertion? Brian Campbell
- Re: [OAUTH-WG] more than one assertion? Eran Hammer-Lahav
- Re: [OAUTH-WG] more than one assertion? Brian Campbell
- Re: [OAUTH-WG] more than one assertion? Eran Hammer-Lahav
- Re: [OAUTH-WG] more than one assertion? Brian Eaton
- Re: [OAUTH-WG] more than one assertion? Chuck Mortimore
- Re: [OAUTH-WG] more than one assertion? David Recordon
- Re: [OAUTH-WG] more than one assertion? Brian Campbell
- Re: [OAUTH-WG] more than one assertion? David Recordon
- Re: [OAUTH-WG] more than one assertion? Torsten Lodderstedt
- Re: [OAUTH-WG] more than one assertion? Eran Hammer-Lahav
- Re: [OAUTH-WG] more than one assertion? Brian Campbell
- Re: [OAUTH-WG] more than one assertion? Brian Campbell
- Re: [OAUTH-WG] more than one assertion? Anthony Nadalin
- Re: [OAUTH-WG] more than one assertion? Eran Hammer-Lahav
- Re: [OAUTH-WG] more than one assertion? Torsten Lodderstedt
- Re: [OAUTH-WG] more than one assertion? Zeltsan, Zachary (Zachary)
- Re: [OAUTH-WG] more than one assertion? Eran Hammer-Lahav
- Re: [OAUTH-WG] more than one assertion? Anthony Nadalin
- Re: [OAUTH-WG] more than one assertion? Anthony Nadalin
- Re: [OAUTH-WG] more than one assertion? Torsten Lodderstedt
- Re: [OAUTH-WG] more than one assertion? Anthony Nadalin