Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-v2

Justin Richer <jricher@mitre.org> Mon, 06 February 2012 19:50 UTC

Return-Path: <jricher@mitre.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0B821F863B for <oauth@ietfa.amsl.com>; Mon, 6 Feb 2012 11:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhiCND0akROO for <oauth@ietfa.amsl.com>; Mon, 6 Feb 2012 11:50:28 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id E220D21F862D for <oauth@ietf.org>; Mon, 6 Feb 2012 11:50:25 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 5B6DE21B1057; Mon, 6 Feb 2012 14:50:23 -0500 (EST)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 3C5D821B0BFE; Mon, 6 Feb 2012 14:50:23 -0500 (EST)
Received: from [129.83.50.12] (129.83.31.51) by IMCCAS04.MITRE.ORG (129.83.29.81) with Microsoft SMTP Server (TLS) id 14.1.339.1; Mon, 6 Feb 2012 14:50:22 -0500
Message-ID: <4F302EB0.9070305@mitre.org>
Date: Mon, 06 Feb 2012 14:49:04 -0500
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Eran Hammer <eran@hueniverse.com>
References: <6B9B0CEF7F409D439E78288D8665BD8FAEAC63@oakmont.llu.ad.lluahsc.org> <90C41DD21FB7C64BB94121FBBC2E723453AADDD18C@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723453AADDD18C@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Content-Type: multipart/alternative; boundary="------------010505050109060506010007"
X-Originating-IP: [129.83.31.51]
Cc: OAuth WG <oauth@ietf.org>, "Thomas, Christopher (LLU)" <cwthomas@llu.edu>
Subject: Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-v2
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 06 Feb 2012 19:50:29 -0000

+1 for consistent examples.

  -- Justin

On 02/06/2012 02:35 PM, Eran Hammer wrote:
>
> Sending to the right place.
>
> *From:*Thomas, Christopher (LLU) [mailto:cwthomas@llu.edu]
> *Sent:* Monday, February 06, 2012 11:33 AM
> *To:* draft-ietf-oauth-v2@tools.ietf.org
> *Subject:* Mail regarding draft-ietf-oauth-v2
>
> Hello,
>
> I'm looking into implementing the Oauth2 spec for a work project and I 
> think I ran into an issue with the version 23 documentation. According 
> to the Oauth2 documentation, a client can send it's credentials one of 
> two ways: 1) via HTTP Basic Auth 2) via the request body parameters. 
> Section 2.3.1 says "....the HTTP Basic authentication scheme as 
> defined in [RFC2617] to authenticate with the authorization server.  
> The client identifier is used as the username, and the client password 
> is           used as the password."
>
> The example given in Section 2.3.1 is:
>
> Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
>
> According to RFC2617 Section 2, the value of the credential is a 
> base64 representation of "username:password" (no quotes). This means 
> when the value is decoded, it is "s6BhdRkqt3:gX1fBat3bV". So, 
> according to the HTTP Basic Auth example, the client_id is s6BhdRkqt3 
> and the client_secret is gX1fBat3bV. Just below the basic auth example 
> is the request body example:
>
> POST /token HTTP/1.1
>
>      Host: server.example.com
>
>      Content-Type: application/x-www-form-urlencoded;charset=UTF-8
>
>      grant_type=refresh_token&refresh_token=tGzv3JOkF0XG5Qx2TlKWIA
>
> &client_id=s6BhdRkqt3&client_secret=7Fjfp0ZBr1KtDRbnfVdmIw
>
> In the request body example, the client_secret does not match the 
> client_secret in the HTTP Basic Auth example. I think the two should 
> match for consistency. I propose the change that is in the patch 
> attached to this email.
>
> Thank you for considering my suggestion.
>
> Chris
>
> Christopher Thomas, BA --- Systems Analyst/
> /LOMA LINDA UNIVERSITY | Information Systems
>
> Loma Linda University, Loma Linda, California 92350
> x87866 or (909) 558-7866
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth