Re: [OAUTH-WG] same-origin policy

Eran Hammer-Lahav <eran@hueniverse.com> Fri, 30 April 2010 15:48 UTC

Return-Path: <eran@hueniverse.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 343543A6B0A for <oauth@core3.amsl.com>; Fri, 30 Apr 2010 08:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599]
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 O4DdRqxKvFL5 for <oauth@core3.amsl.com>; Fri, 30 Apr 2010 08:48:05 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by core3.amsl.com (Postfix) with SMTP id CA0683A6B02 for <oauth@ietf.org>; Fri, 30 Apr 2010 08:48:04 -0700 (PDT)
Received: (qmail 15057 invoked from network); 30 Apr 2010 15:47:49 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 30 Apr 2010 15:47:49 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Fri, 30 Apr 2010 08:47:47 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>, OAuth WG <oauth@ietf.org>
Date: Fri, 30 Apr 2010 08:46:39 -0700
Thread-Topic: [OAUTH-WG] same-origin policy
Thread-Index: Acrn/ZeK7OLXJrTKQSWD19+9KX5Q3AAfrODw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723439321772F8@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <u2n74caaad21004291738ua47de12aob707d77e46e47adb@mail.gmail.com>
In-Reply-To: <u2n74caaad21004291738ua47de12aob707d77e46e47adb@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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 15:48:06 -0000

This language was requested by Brian.

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Marius Scurtescu
> Sent: Thursday, April 29, 2010 5:39 PM
> To: OAuth WG
> Subject: [OAUTH-WG] same-origin policy
> 
> 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
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth