IETF Logo Mail Archive

Re: [OAUTH-WG] sites with wildcard

Marius Scurtescu <mscurtescu@google.com> Wed, 12 May 2010 16:47 UTC

Return-Path: <mscurtescu@google.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 D2FFF3A6955 for <oauth@core3.amsl.com>; Wed, 12 May 2010 09:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.809
X-Spam-Level:
X-Spam-Status: No, score=-105.809 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 hPSS+n2M6Fae for <oauth@core3.amsl.com>; Wed, 12 May 2010 09:47:37 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id C82F128C23D for <oauth@ietf.org>; Wed, 12 May 2010 09:28:14 -0700 (PDT)
Received: from wpaz1.hot.corp.google.com (wpaz1.hot.corp.google.com [172.24.198.65]) by smtp-out.google.com with ESMTP id o4CGS0ln004439 for <oauth@ietf.org>; Wed, 12 May 2010 09:28:03 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273681683; bh=hD3AjE7832pLeQD9Me1hFayOZ7Y=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=eKdySICJ953C/HtYIBsD+v5KbrjR4MElbSUJFzEdRzY0eoKBVoU82bC4DWaD7CUKV IdE7Zv4O4QvZ1NCn/CC4g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=iD8D7C0Rz2gvTa13mhF3JdKIdBBsxmAzIox6asGlKjVtwbTi0GaG0nxD1xpu8LqN+ eDQXk87emz97rzWsV3Snw==
Received: from pzk41 (pzk41.prod.google.com [10.243.19.169]) by wpaz1.hot.corp.google.com with ESMTP id o4CGRxGC022679 for <oauth@ietf.org>; Wed, 12 May 2010 09:27:59 -0700
Received: by pzk41 with SMTP id 41so126062pzk.10 for <oauth@ietf.org>; Wed, 12 May 2010 09:27:59 -0700 (PDT)
Received: by 10.140.58.1 with SMTP id g1mr4990567rva.138.1273681676279; Wed, 12 May 2010 09:27:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.125.21 with HTTP; Wed, 12 May 2010 09:27:36 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126331480A@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E11263284E5B@WSMSG3153V.srv.dir.telstra.com> <7C01E631FF4B654FA1E783F1C0265F8C4A426BD7@TK5EX14MBXC117.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E112632852F1@WSMSG3153V.srv.dir.telstra.com> <AANLkTin6RXbIPAqeEuPKwrbgKbNwTsL2KGcNLlzU8xLc@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1126331480A@WSMSG3153V.srv.dir.telstra.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 12 May 2010 09:27:36 -0700
Message-ID: <AANLkTinG9ovAEyxjpUEY1bdmDk6z8Z-g2Y7zMpy-JE5i@mail.gmail.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] sites with wildcard
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: Wed, 12 May 2010 16:47:37 -0000

On Tue, May 11, 2010 at 5:37 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:
> Marius,
>
>>> Should it send the token when getting the photos?
>
>> I would say definitely not. If the client gets back a 403 with
>> discovery info that points to the same authz server and approved
>> scopes, only then could the client re-try with a token.
>
>> Would that work?
>
> No. That would be totally insecure.
>
> Any site can return a 403 and list, say, Google as its authz server so any site (good or bad) could get a client to reveal its Google token.

Good point.

Thanks for clarifying all my questions.

Marius

v2.23.0 | Report a Bug | By Email