Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
Torsten Lodderstedt <torsten@lodderstedt.net> Fri, 03 September 2010 15:54 UTC
Return-Path: <torsten@lodderstedt.net>
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 1AE7E3A6950 for <oauth@core3.amsl.com>; Fri, 3 Sep 2010 08:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.706
X-Spam-Level:
X-Spam-Status: No, score=-0.706 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_QP_LONG_LINE=1.396]
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 6-z65CYktu01 for <oauth@core3.amsl.com>; Fri, 3 Sep 2010 08:54:50 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.36]) by core3.amsl.com (Postfix) with ESMTP id 98B003A68DE for <oauth@ietf.org>; Fri, 3 Sep 2010 08:54:49 -0700 (PDT)
Received: from [80.187.101.33] (helo=[10.217.92.145]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OrYbj-0000DM-56; Fri, 03 Sep 2010 17:55:16 +0200
References: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE13@P3PW5EX1MB01.EX1.SECURESERVER.NET> <1283462840.3809.42.camel@localhost.localdomain>
In-Reply-To: <1283462840.3809.42.camel@localhost.localdomain>
Mime-Version: 1.0 (iPhone Mail 8A400)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Message-Id: <5536EDEC-DBB8-42F5-8D76-4A9968F4C000@lodderstedt.net>
X-Mailer: iPhone Mail (8A400)
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Date: Fri, 03 Sep 2010 17:54:28 +0200
To: Justin Richer <jricher@mitre.org>
X-Df-Sender: 141509
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: Fri, 03 Sep 2010 15:54:51 -0000
+1 we just discussed the need for adding grant types in order support Telekom-specific user authentication mechanisms. So this proposal comes right in time :-) regards, Torsten. Am 02.09.2010 um 23:27 schrieb Justin Richer <jricher@mitre.org>: > +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 >> >> >> >> > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- 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