IETF Logo Mail Archive

Re: [OAUTH-WG] 'Scope' parameter proposal

Eran Hammer-Lahav <eran@hueniverse.com> Thu, 22 April 2010 19: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 D176E28C13F for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 12:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level:
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 K3NTqR7skLxN for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 12:48:19 -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 9E6DD3A68C1 for <oauth@ietf.org>; Thu, 22 Apr 2010 12:41:23 -0700 (PDT)
Received: (qmail 8157 invoked from network); 22 Apr 2010 19:41:12 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 22 Apr 2010 19:41:12 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Thu, 22 Apr 2010 12:41:12 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Brian Eaton <beaton@google.com>
Date: Thu, 22 Apr 2010 12:41:02 -0700
Thread-Topic: [OAUTH-WG] 'Scope' parameter proposal
Thread-Index: AcriUwXUES61COq5S2Gea8MmruWSNQAAKLnw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723438E5C7FD4A@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <C7F1D1FC.32809%eran@hueniverse.com> <0D5497F5-75A7-4A42-9A5E-9C2310162B18@jkemp.net> <90C41DD21FB7C64BB94121FBBC2E723438E5C7F30A@P3PW5EX1MB01.EX1.SECURESERVER.NET> <g2mdaf5b9571004221036j5d6837f6z4d7959d69a3cbb2b@mail.gmail.com> <BB02FD4F-071E-4FF5-B3D0-F8D3FA22FEEE@jkemp.net> <90C41DD21FB7C64BB94121FBBC2E723438E5C7FD26@P3PW5EX1MB01.EX1.SECURESERVER.NET> <h2ldaf5b9571004221235tb844eb6ah623955979526c1b6@mail.gmail.com>
In-Reply-To: <h2ldaf5b9571004221235tb844eb6ah623955979526c1b6@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
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] 'Scope' parameter proposal
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: Thu, 22 Apr 2010 19:48:19 -0000

Drop the 'scope' parameter as well and we're on the same page.

EHL

> -----Original Message-----
> From: Brian Eaton [mailto:beaton@google.com]
> Sent: Thursday, April 22, 2010 12:36 PM
> To: Eran Hammer-Lahav
> Cc: John Kemp; OAuth WG
> Subject: Re: [OAUTH-WG] 'Scope' parameter proposal
> 
> On Thu, Apr 22, 2010 at 12:07 PM, Eran Hammer-Lahav
> <eran@hueniverse.com> wrote:
> > If we are not going to enable a client to access a protected resource
> > hosted by an unfamiliar server, we need to stop pretending this
> > (alone) is about interop. In other words, if we take this approach we
> > are mandating paperwork to make the protocol work, at least based on
> > this single specification. We can also drop advertising the authorization and
> token endpoints in a 401 or really *any* parameter in a WWW-Authenticate
> response.
> 
> I think dropping the advertisements is the right thing to do.
> 
> I'm hopeful that either PoCo or the IMAP SASL/OAuth work ends up showing
> how automatic interop is possible.
> 
> But I'd hate to have OAuth2 recommend something that doesn't actually
> work.
> 
> Cheers,
> Brian

v2.23.0 | Report a Bug | By Email