IETF Logo Mail Archive

Re: [OAUTH-WG] Issue: Split the authorization endpoint into two endpoints

"Manger, James H" <James.H.Manger@team.telstra.com> Sat, 17 April 2010 12:05 UTC

Return-Path: <James.H.Manger@team.telstra.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 905453A6A13 for <oauth@core3.amsl.com>; Sat, 17 Apr 2010 05:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.501
X-Spam-Level:
X-Spam-Status: No, score=0.501 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_05=-1.11, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 1yS9z9f4eBwP for <oauth@core3.amsl.com>; Sat, 17 Apr 2010 05:05:10 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by core3.amsl.com (Postfix) with ESMTP id 4A1783A6944 for <oauth@ietf.org>; Sat, 17 Apr 2010 05:05:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,226,1270389600"; d="scan'208,217";a="1104377"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipobni.tcif.telstra.com.au with ESMTP; 17 Apr 2010 22:05:00 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5953"; a="1128890"
Received: from wsmsg3703.srv.dir.telstra.com ([172.49.40.171]) by ipcani.tcif.telstra.com.au with ESMTP; 17 Apr 2010 22:05:00 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3703.srv.dir.telstra.com ([172.49.40.171]) with mapi; Sat, 17 Apr 2010 22:04:59 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>, Torsten Lodderstedt <torsten@lodderstedt.net>, OAuth WG <oauth@ietf.org>
Date: Sat, 17 Apr 2010 22:04:57 +1000
Thread-Topic: [OAUTH-WG] Issue: Split the authorization endpoint into two endpoints
Thread-Index: AcreBXyhwMO7BvK2S/y39OthXsgISQAHaMLjAABYyYA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E1125759234A@WSMSG3153V.srv.dir.telstra.com>
References: <4BC96CF4.7050009@lodderstedt.net> <C7EEECD1.32476%eran@hueniverse.com>
In-Reply-To: <C7EEECD1.32476%eran@hueniverse.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E1125759234AWSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Issue: Split the authorization endpoint into two endpoints
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: Sat, 17 Apr 2010 12:05:11 -0000

> How would use differentiate between the username and password profile and the client credentials profile, if you are using Basic or Digest?



Removing the client_secret from both flows still leaves one flow with ‘username’ and ‘password’ POST parameters (of the user, not client), which indicates whether a token acting for the user or client is desired.

v2.23.0 | Report a Bug | By Email