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

"Manger, James H" <James.H.Manger@team.telstra.com> Sat, 17 April 2010 02:03 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 F24803A6A2D for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 19:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.189
X-Spam-Level:
X-Spam-Status: No, score=-0.189 tagged_above=-999 required=5 tests=[AWL=0.712, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, 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 tIoD7TFycSXZ for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 19:03:01 -0700 (PDT)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by core3.amsl.com (Postfix) with ESMTP id EFBEA3A6986 for <oauth@ietf.org>; Fri, 16 Apr 2010 19:02:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,223,1270389600"; d="scan'208";a="1095115"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipocni.tcif.telstra.com.au with ESMTP; 17 Apr 2010 12:02:50 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5953"; a="1124594"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipcani.tcif.telstra.com.au with ESMTP; 17 Apr 2010 12:02:50 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Sat, 17 Apr 2010 12:02:50 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Luke Shepard <lshepard@facebook.com>, John Kemp <john@jkemp.net>
Date: Sat, 17 Apr 2010 12:02:45 +1000
Thread-Topic: [OAUTH-WG] Issue: Split the authorization endpoint into two endpoints
Thread-Index: AcrdCitsLp+WWglvQMKPMWBhihZtKQAezmZQABLw0xA=
Message-ID: <255B9BB34FB7D647A506DC292726F6E11257592315@WSMSG3153V.srv.dir.telstra.com>
References: <C7ECABE0.32344%eran@hueniverse.com> <255B9BB34FB7D647A506DC292726F6E11257481003@WSMSG3153V.srv.dir.telstra.com> <9E18821D-E128-468A-9778-9D9D049B716F@jkemp.net> <2513A610118CC14C8E622C376C8DEC93D54D66DCF7@SC-MBXC1.TheFacebook.com>
In-Reply-To: <2513A610118CC14C8E622C376C8DEC93D54D66DCF7@SC-MBXC1.TheFacebook.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: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
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 02:03:02 -0000

>> In either case, we should not restrict the access token URL to POST-only.
>> A GET request is just as secure and can be much easier to write code for

> If you are using GET, then refresh tokens and client secrets will end
> up side by side in web server log files.

These are exactly the sort of reasons why client authentication should be any "normal" auth scheme, and not an OAuth-special client_secret POST parameter. That fails for PUT, DELETE, and POST with a non-form body; and the security changes with GET.

--
James Manger