IETF Logo Mail Archive

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

Brian Eaton <beaton@google.com> Thu, 22 April 2010 18:38 UTC

Return-Path: <beaton@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 84A543A6C24 for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 11:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[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 pBZ9d9uGBer3 for <oauth@core3.amsl.com>; Thu, 22 Apr 2010 11:38:21 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 739F128C218 for <oauth@ietf.org>; Thu, 22 Apr 2010 11:33:18 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [10.3.21.12]) by smtp-out.google.com with ESMTP id o3MIX5Be009485 for <oauth@ietf.org>; Thu, 22 Apr 2010 11:33:07 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271961187; bh=+L9BPGXqLUPxOEmgHFGD8Fxk+ho=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=jEX/YFoSyHra+1ge2UACd1bP4TIQ8i6cPq3NWT3TSkKX/xirs23Le+3csFwf/zUFy +WgUIvABMeiqU1P9paDHw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=PR44XWEiyJKrUXwLs/eNcEIh4lud294ZAw98VXf9Wwzjo8FjaykIgxvtISLCYesqz nEweQQoj03eMovCJ3DwQw==
Received: from pzk29 (pzk29.prod.google.com [10.243.19.157]) by hpaq12.eem.corp.google.com with ESMTP id o3MIX3Qr031953 for <oauth@ietf.org>; Thu, 22 Apr 2010 20:33:04 +0200
Received: by pzk29 with SMTP id 29so846548pzk.3 for <oauth@ietf.org>; Thu, 22 Apr 2010 11:33:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.202.10 with HTTP; Thu, 22 Apr 2010 11:33:03 -0700 (PDT)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723438E5C7FCFA@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> <90C41DD21FB7C64BB94121FBBC2E723438E5C7FCD4@P3PW5EX1MB01.EX1.SECURESERVER.NET> <z2wdaf5b9571004221121m611c6a4ay6d636c440bb48d06@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E723438E5C7FCFA@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 22 Apr 2010 11:33:03 -0700
Received: by 10.143.154.37 with SMTP id g37mr4743805wfo.35.1271961183232; Thu, 22 Apr 2010 11:33:03 -0700 (PDT)
Message-ID: <i2ldaf5b9571004221133y75ca7739i2063cd020757d78@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
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 18:38:22 -0000

On Thu, Apr 22, 2010 at 11:30 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> What makes this so much different from Basic? Instead of using a flow the browser
> simply asks the user for a set of credentials. Once it has a set, it reuses it based on realm.

Those rules aren't practical or correct for most APIs.

Remember that basic auth was designed for people using web browsers.

v2.23.0 | Report a Bug | By Email