IETF Logo Mail Archive

Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08.txt WGLC comments

Julian Reschke <julian.reschke@gmx.de> Wed, 12 October 2011 18:24 UTC

Return-Path: <julian.reschke@gmx.de>
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 CE1CA21F8CA0 for <oauth@ietfa.amsl.com>; Wed, 12 Oct 2011 11:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.849
X-Spam-Level:
X-Spam-Status: No, score=-104.849 tagged_above=-999 required=5 tests=[AWL=-2.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 EyjlvbW-pcD1 for <oauth@ietfa.amsl.com>; Wed, 12 Oct 2011 11:24:04 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id F158921F8C9F for <oauth@ietf.org>; Wed, 12 Oct 2011 11:24:03 -0700 (PDT)
Received: (qmail invoked by alias); 12 Oct 2011 18:24:00 -0000
Received: from p5DCC9E25.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.158.37] by mail.gmx.net (mp046) with SMTP; 12 Oct 2011 20:24:00 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1873s4hHyw7Up+UKjA+mHcERAC0exITTZ7QbPW3RL ACnJyc/42VgJCz
Message-ID: <4E95DB3B.2040802@gmx.de>
Date: Wed, 12 Oct 2011 20:23:55 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Mike Jones <Michael.Jones@microsoft.com>
References: <20110727131700.23436.11568.idtracker@ietfa.amsl.com> <4E1F6AAD24975D4BA5B16804296739434986822D@TK5EX14MBXC202.redmond.corp.microsoft.com> <CAC4RtVBx-WrxbXE-DxvEp3EsE3q6oEcrv9XWxteB11AjPMK3Hg@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11289635128@WSMSG3153V.srv.dir.telstra.com> <1314767698.36186.YahooMailNeo@web31808.mail.mud.yahoo.com> <255B9BB34FB7D647A506DC292726F6E1128DB1DE6E@WSMSG3153V.srv.dir.telstra.com> <1318350042.89721.YahooMailNeo@web31810.mail.mud.yahoo.com> <255B9BB34FB7D647A506DC292726F6E1129072392A@WSMSG3153V.srv.dir.telstra.com> <4E955C01.40603@gmx.de> <4E1F6AAD24975D4BA5B16804296739435C238C90@TK5EX14MBXC284.redmond.corp.microsoft.com> <4E95A987.1000203@gmx.de> <4E1F6AAD24975D4BA5B16804296739435C239299@TK5EX14MBXC284.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739435C239299@TK5EX14MBXC284.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-v2-bearer-08.txt WGLC comments
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: Wed, 12 Oct 2011 18:24:05 -0000

On 2011-10-12 20:02, Mike Jones wrote:
> The syntax in HTTPbis is:
>      credentials = auth-scheme [ 1*SP ( b64token / #auth-param ) ]
>
> The syntax in Bearer 09 is:
>     credentials = "Bearer" 1*SP ( b64token / #auth-param )
>
> As this conforms to HTTPbis, I don't see a problem.  I think HTTPbis and Bearer are both fine as-is.

The intent is that a scheme uses one of the two constructs, not both.

Bearer can't use auth-params and b64tokens in the same challenge, so 
it's unclear to me how this is supposed to work.

If you have a notation where you can express the bearer token as 
auth-param then why don't you *always* use it and get rid of the 
b64token construct?

Best regards, Julian

v2.23.0 | Report a Bug | By Email