[OAUTH-WG] same-origin policy

Marius Scurtescu <mscurtescu@google.com> Fri, 30 April 2010 00:39 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 85DAE3A6812 for <oauth@core3.amsl.com>; Thu, 29 Apr 2010 17:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.536
X-Spam-Level:
X-Spam-Status: No, score=-100.536 tagged_above=-999 required=5 tests=[AWL=-0.973, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, 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 uByplRCQsg3x for <oauth@core3.amsl.com>; Thu, 29 Apr 2010 17:39:35 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 66BB83A63D3 for <oauth@ietf.org>; Thu, 29 Apr 2010 17:39:35 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [10.3.21.1]) by smtp-out.google.com with ESMTP id o3U0dKUn027306 for <oauth@ietf.org>; Thu, 29 Apr 2010 17:39:20 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1272587960; bh=d0HDJOSFfBX0/NgfiPqEEoKrwqM=; h=MIME-Version:From:Date:Message-ID:Subject:To:Content-Type; b=BvJ7D8vF2i/IwX0p7o4j9f0cZrK/TlpNGlSWBTrJ8jD7K4rlTt65CAI1xxMl42wAi M8MojZSoSfIxpWz//t6Mw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:from:date:message-id:subject:to:content-type:x-system-of-record; b=uV/Z3u3k2ViM/kAvYg1xlx1NO529XYUQxeOvaf4e+3aTKweByhpoAG9r42y4s14Hx Xmz/rRTiK5E1aqMcqBlmQ==
Received: from pxi1 (pxi1.prod.google.com [10.243.27.1]) by hpaq1.eem.corp.google.com with ESMTP id o3U0dIqX016768 for <oauth@ietf.org>; Thu, 29 Apr 2010 17:39:19 -0700
Received: by pxi1 with SMTP id 1so3341457pxi.8 for <oauth@ietf.org>; Thu, 29 Apr 2010 17:39:18 -0700 (PDT)
Received: by 10.141.2.2 with SMTP id e2mr209337rvi.263.1272587958154; Thu, 29 Apr 2010 17:39:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.14.15 with HTTP; Thu, 29 Apr 2010 17:38:58 -0700 (PDT)
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 29 Apr 2010 17:38:58 -0700
Message-ID: <u2n74caaad21004291738ua47de12aob707d77e46e47adb@mail.gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-System-Of-Record: true
Subject: [OAUTH-WG] same-origin policy
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: Fri, 30 Apr 2010 00:39:36 -0000

Section 3.5.1, version 01, says: "These clients cannot keep client
secrets confidential and the authentication of the client is based on
the user-agent's same-origin policy."

I don't think that the same-origin policy comes into play in this
case. Authentication of the client is based only on the end-user
validating the redirection URI.

Marius