IETF Logo Mail Archive

Re: [OAUTH-WG] Report an authentication issue

Dick Hardt <dick.hardt@gmail.com> Fri, 29 June 2012 18:14 UTC

Return-Path: <dick.hardt@gmail.com>
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 50D6521F884A for <oauth@ietfa.amsl.com>; Fri, 29 Jun 2012 11:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level:
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 rGjbldLG6Fn4 for <oauth@ietfa.amsl.com>; Fri, 29 Jun 2012 11:14:15 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 92E0321F86F4 for <oauth@ietf.org>; Fri, 29 Jun 2012 11:14:15 -0700 (PDT)
Received: by dacx6 with SMTP id x6so4885502dac.31 for <oauth@ietf.org>; Fri, 29 Jun 2012 11:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=pWGrLYi8Kv7DgJNpo3BkBPpXY2QmPZqpu+T88IKwKF0=; b=0Rn7reFup2k5TYYktlfj0HLzpRbCz9cyOXRKUZIn9bZ96jRHeANnD5aFM3Gs5AhVl/ DPIUX6nLoIaK872fZJ1+R/l7AJxqheCmXqlXK1PvUFHagwtvFY8QZaru4yoeDVmBSUOm Y06mIk4BVEhHdrjUczjKVJbcTrJDd9TCzQhs7SgjnBDP/rQWnU/JbzigC5B28/g1Y4JA VzGgFKq17n/nXxz86a5dyAnLQkVyTvgwy3BzJ3ofkAJi2/9enDGLgXD4FACcNB2SEbJR ibdX7xaOQ/9nx4KH4UaTtDUGdCOm8D6/MbK+2zlmOAI78Wqw7+1XncOsGUH0FK5Ruvrv yR+A==
Received: by 10.68.226.65 with SMTP id rq1mr8765457pbc.25.1340993655399; Fri, 29 Jun 2012 11:14:15 -0700 (PDT)
Received: from [10.0.0.4] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id mt9sm6120323pbb.14.2012.06.29.11.14.12 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 29 Jun 2012 11:14:13 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="iso-8859-1"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <4DD23AA1-C319-477A-B0CB-34E558EB7FCC@ve7jtb.com>
Date: Fri, 29 Jun 2012 11:14:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C18C43D-AC63-465A-ADC2-966CE7F38685@gmail.com>
References: <CAEEmcpEcNqNHwfVozD-NtfkruiB-v0MTszwNL4cob2rL=QQTSA@mail.gmail.com> <4FE223E4.6060307@mitre.org> <4FE226BC.6010403@alcatel-lucent.com> <59E470B10C4630419ED717AC79FCF9A910889AB5@BL2PRD0410MB363.namprd04.prod.outlook.com> <CABzCy2CLe_DVcxiD1EasuhtG1_6+6tCtV5TckZ80fvqyjan_bA@mail.gmail.com> <59E470B10C4630419ED717AC79FCF9A917052BC8@SN2PRD0410MB370.namprd04.prod.outlook.com> <4FE37D38.1030407@gmail.com> <CABzCy2A_zJ3vaauoo6VwsmLWsTesdTujuQ4dHdVpc5Nh==iEFg@mail.gmail.com> <59E470B10C4630419ED717AC79FCF9A91A2C8949@CH1PRD0410MB369.namprd04.prod.outlook.com> <CABzCy2DzmNgmMALNfc1qp95fwD2WULb-49Dk yLiZnjXngAmaPg@mail.gmail.com> <59E470B10C4630419ED717AC79FCF9A91A2D1309@CH1PRD0410MB369.namprd04.prod.outlook.com> <496AFB1D-A609-4188-B92D-2185E8880388@ve7jtb.com> <59E470B10C4630419ED717AC79FCF9A91A2D13C9@CH1PRD0410MB369.namprd04.prod.outlook.com> <67F8B633-E4C8-42F6-B84C-FDBC337B7EEA@ve7jtb.com> <04C05FAA-63BC-4441-8540-36280E40DB98@adobe.com> <4FEDE4AF.9030107@mitre.org> <4 DD23AA1-C319-477A-B0CB-34E558EB7FCC@ve7jtb.com>
To: John Bradley <ve7jtb@ve7jtb.com>
X-Mailer: Apple Mail (2.1278)
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Report an authentication issue
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: Fri, 29 Jun 2012 18:14:16 -0000

On Jun 29, 2012, at 11:06 AM, John Bradley wrote:

> It is nice to know that I may occasionally be correct:)

You must be delighted when it happens! ;)

> While you may assume that it is reasonable for a client with a code to make a request to the token endpoint including it's client_id and the server to only give out the access token if the client_id in the token request matches the one in the original authorization request.   However the spec specifically doesn't require that.

I think that is an error in the spec and should be changed, or text adding saying that the client_id SHOULD be checked.

-- Dick

v2.23.0 | Report a Bug | By Email