Re: [OAUTH-WG] Simpilfying use of assertions when requesting an access token
Justin Richer <jricher@mitre.org> Thu, 02 September 2010 21:26 UTC
Return-Path: <jricher@mitre.org>
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 8E8A83A688C for <oauth@core3.amsl.com>; Thu, 2 Sep 2010 14:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.502
X-Spam-Level:
X-Spam-Status: No, score=-6.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 JDD6MSP7YnS2 for <oauth@core3.amsl.com>; Thu, 2 Sep 2010 14:26:52 -0700 (PDT)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 801573A69BC for <oauth@ietf.org>; Thu, 2 Sep 2010 14:26:52 -0700 (PDT)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o82LRLC4005428 for <oauth@ietf.org>; Thu, 2 Sep 2010 17:27:21 -0400
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id o82LRKNe005398; Thu, 2 Sep 2010 17:27:21 -0400
Received: from [129.83.50.65] (129.83.50.65) by imchub2.MITRE.ORG (129.83.29.74) with Microsoft SMTP Server id 8.2.254.0; Thu, 2 Sep 2010 17:27:20 -0400
From: Justin Richer <jricher@mitre.org>
To: Eran Hammer-Lahav <eran@hueniverse.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE13@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343B3F35BE13@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 02 Sep 2010 17:27:20 -0400
Message-ID: <1283462840.3809.42.camel@localhost.localdomain>
MIME-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 8bit
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:26:53 -0000
+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