[OAUTH-WG] Draf 10 OAuth chapter 2.1 question

Kristoffer Gronowski <kristoffer.gronowski@ericsson.com> Tue, 26 October 2010 17:17 UTC

Return-Path: <kristoffer.gronowski@ericsson.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 8A9C63A69C5 for <oauth@core3.amsl.com>; Tue, 26 Oct 2010 10:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id zcwBFvU0kXa6 for <oauth@core3.amsl.com>; Tue, 26 Oct 2010 10:17:17 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com []) by core3.amsl.com (Postfix) with ESMTP id 182D13A69CF for <oauth@ietf.org>; Tue, 26 Oct 2010 10:17:15 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o9QHd04b024900 for <oauth@ietf.org>; Tue, 26 Oct 2010 12:39:01 -0500
Received: from EUSAACMS0701.eamcs.ericsson.se ([]) by eusaamw0711.eamcs.ericsson.se ([]) with mapi; Tue, 26 Oct 2010 13:18:54 -0400
From: Kristoffer Gronowski <kristoffer.gronowski@ericsson.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Date: Tue, 26 Oct 2010 13:18:53 -0400
Thread-Topic: Draf 10 OAuth chapter 2.1 question
Thread-Index: Act1MZiEzxFBD0XQQ1+jz60a7Grs0gAABllQ
Message-ID: <C0AC8FAB6849AB4FADACCC70A949E2F10929F40271@EUSAACMS0701.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [OAUTH-WG] Draf 10 OAuth chapter 2.1 question
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: Tue, 26 Oct 2010 17:17:26 -0000


Just wondering for clarification on the example.

For example (line breaks are for display purposes only):

     POST /token HTTP/1.1
     Host: server.example.com
     Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
     Content-Type: application/x-www-form-urlencoded


   Alternatively, the client MAY include the password in the request
   body using the following parameter:

   client_secret  REQUIRED.  The client password.

   For example (line breaks are for display purposes only):

     POST /token HTTP/1.1
     Host: server.example.com
     Content-Type: application/x-www-form-urlencoded


When searching for the password should also the user part be used?
If you Base64 decode czZCaGRSa3F0MzpnWDFmQmF0M2JW you get:

So it is sending client_id:client_secret.
In that case the FORM has a redundant client_id parameter.
Should an implementation search for client_id in the basic header or not?

If not I guess that a valid basic auth header could be just :client_secret or in this case :gX1fBat3bV?

Might be good with a clarification here.

BR Kristoffer