Re: [oauth] OAUTH Charter Proposal

Blaine Cook <romeda@gmail.com> Mon, 02 February 2009 16:43 UTC

Return-Path: <oauth-bounces@ietf.org>
X-Original-To: oauth-archive@ietf.org
Delivered-To: ietfarch-oauth-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D42228C154; Mon, 2 Feb 2009 08:43:00 -0800 (PST)
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 6B5B03A6B88 for <oauth@core3.amsl.com>; Mon, 2 Feb 2009 08:42:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 uDPimDB1h3KA for <oauth@core3.amsl.com>; Mon, 2 Feb 2009 08:42:57 -0800 (PST)
Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by core3.amsl.com (Postfix) with ESMTP id 2C8563A68AC for <oauth@ietf.org>; Mon, 2 Feb 2009 08:42:57 -0800 (PST)
Received: by ewy14 with SMTP id 14so1949453ewy.13 for <oauth@ietf.org>; Mon, 02 Feb 2009 08:42:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wM0r9gBiPQWwfe8/pRycLf/WjvQ0V9ja6BJm4CJWvik=; b=DUJJsY35LXfHHoezFWBKLrfkH7RJpqDVcJra4Y8QuoaKyqNlPNt1ufsQx6UZBs8FW3 8kQ0YDV/Fs7cjDjkx1rQBjHs5ygDamqVuUfUje65/Zoeaxmo4/OMhK3JAcWGowrf/3MQ djivDHJKkYNgd5B4xqvl5IoGMHRAlPoUB9W5Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AQHuc/Zo9YKcYH4AirCZ3YvEG4jgIBO0pi2rDTPNjrpW2rMcHVw87GVSxUVidKy5PA ASfHxzyeemfHPLtfm7l56jX5gqejeqL28iMlK13hTRAoqeXznATQmtmN1m1B+zp0vHyG Z8tXypg5xMfpds68WXcB9PNGJFO8bXGLbpQME=
MIME-Version: 1.0
Received: by 10.210.111.4 with SMTP id j4mr1089514ebc.1.1233592956968; Mon, 02 Feb 2009 08:42:36 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E7234127C939A08@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <033101c98303$e6fde7f0$0201a8c0@nsnintra.net> <4986F954.1090001@aol.com> <90C41DD21FB7C64BB94121FBBC2E7234127C939A08@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 02 Feb 2009 16:42:36 +0000
Message-ID: <d37b4b430902020842j444cc187j7e332f0badffea47@mail.gmail.com>
From: Blaine Cook <romeda@gmail.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [oauth] OAUTH Charter Proposal
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Oauth bof discussion <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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: oauth-bounces@ietf.org
Errors-To: oauth-bounces@ietf.org

On Mon, Feb 2, 2009 at 4:15 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> How is exchanging credentials equal to authentication?

By exchanging the credentials in a verifiable way (i.e., with secrets
& signing), you're authenticating the consumer as acting on behalf of
the user. If we weren't trying to do *authenticated* requests, then
there wouldn't be any point in hiding (or having) secrets.

> I would not want to use the term API in the charter. While this is the current use case, I view OAuth as part of the 2617 family, and can be used for any HTTP request. I do not think most people consider every HTTP request an API call.

+1 - perhaps the more general "Interface" makes sense? I think OAuth
is actually a bit more general than 2617, in that it's possible to use
it across transport protocols (though in general we should be
targeting HTTP first).

b.
_______________________________________________
oauth mailing list
oauth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth