Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
Eran Hammer-Lahav <eran@hueniverse.com> Thu, 02 September 2010 21:27 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 4D88D3A69BC for <oauth@core3.amsl.com>; Thu, 2 Sep 2010 14:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level:
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599]
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 KK73uQPWblAW for <oauth@core3.amsl.com>; Thu, 2 Sep 2010 14:27:42 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id 588E93A695A for <oauth@ietf.org>; Thu, 2 Sep 2010 14:27:41 -0700 (PDT)
Received: (qmail 12091 invoked from network); 2 Sep 2010 21:28:11 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 2 Sep 2010 21:28:11 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Thu, 2 Sep 2010 14:28:10 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Justin Richer <jricher@mitre.org>
Date: Thu, 02 Sep 2010 14:28:20 -0700
Thread-Topic: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
Thread-Index: ActK5aHmHd2SWfueRAGs3gsxivAjPgAAB81w
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE2D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE13@P3PW5EX1MB01.EX1.SECURESERVER.NET> <1283462840.3809.42.camel@localhost.localdomain>
In-Reply-To: <1283462840.3809.42.camel@localhost.localdomain>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
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, 02 Sep 2010 21:27:46 -0000
Yes. -----Original Message----- From: Justin Richer [mailto:jricher@mitre.org] Sent: Thursday, September 02, 2010 2:27 PM To: Eran Hammer-Lahav Cc: OAuth WG (oauth@ietf.org) Subject: Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token +1 I've never liked the notion of not being able to extend the "grant type" field, and this change addresses that particular gripe. Just so I'm clear here: an extension that defines its own url-defined grant type can also legally add and remove parameters from the endpoint, right? -- Justin On Thu, 2010-09-02 at 17:11 -0400, Eran Hammer-Lahav wrote: > I would like to make this change in -11: > > > > Instead of the current user of the ‘assertion’ grant type – > > > > POST /token HTTP/1.1 > > Host: server.example.com > > Content-Type: application/x-www-form-urlencoded > > > > grant_type=assertion& > > assertion_type=urn%3Aoasis%3Anames%3Atc%3ASAML%3A2.0%3Aassertion& > > assertion=PHNhbWxwOl[...omitted for brevity...]ZT4%3D > > > > Drop the ‘assertion’ grant type and put the assertion type directly in > the grant_type parameter: > > > > POST /token HTTP/1.1 > > Host: server.example.com > > Content-Type: application/x-www-form-urlencoded > > > > grant_type=urn%3Aoasis%3Anames%3Atc%3ASAML%3A2.0%3Aassertion& > > assertion=PHNhbWxwOl[...omitted for brevity...]ZT4%3D > > > > In other words, the grant_type parameter value will be defined as: > > > > - authorization_code > > - password > > - client_credentials > > - refresh_token > > - an abolute URI (extensions) > > > > I considered turning all the values into URIs but found it to be > counter-intuitive. The practice of using “official” short names and > extension URIs is well established and is already the general > architecture used here. This just makes it cleaner. > > > > I ran this idea by Brian Campbell and Chuck Mortimore who are > generally supportive of the idea. > > > > Any objections? > > > > EHL > > > >
- Re: [OAUTH-WG] Simpilfying use of assertions when… Justin Richer
- Re: [OAUTH-WG] Simpilfying use of assertions when… Eran Hammer-Lahav
- [OAUTH-WG] Simpilfying use of assertions when req… Eran Hammer-Lahav
- Re: [OAUTH-WG] Simpilfying use of assertions when… David Recordon
- Re: [OAUTH-WG] Simpilfying use of assertions when… Torsten Lodderstedt
- Re: [OAUTH-WG] Simpilfying use of assertions when… David Waite
- Re: [OAUTH-WG] Simpilfying use of assertions when… David Recordon
- Re: [OAUTH-WG] Simpilfying use of assertions when… Eran Hammer-Lahav
- Re: [OAUTH-WG] Simpilfying use of assertions when… Brian Campbell
- Re: [OAUTH-WG] Simpilfying use of assertions when… Justin Richer
- Re: [OAUTH-WG] Simpilfying use of assertions when… Brian Campbell
- Re: [OAUTH-WG] Simpilfying use of assertions when… Eran Hammer-Lahav
- Re: [OAUTH-WG] Simpilfying use of assertions when… Brian Campbell
- Re: [OAUTH-WG] Simpilfying use of assertions when… Marius Scurtescu
- Re: [OAUTH-WG] Simpilfying use of assertions when… Brian Campbell