IETF Logo Mail Archive

Re: [OAUTH-WG] keeping support for RSA (Was: RE: OAuth 2.0 / Charter)

Brian Eaton <beaton@google.com> Mon, 30 November 2009 21:53 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 7317D3A693C for <oauth@core3.amsl.com>; Mon, 30 Nov 2009 13:53:23 -0800 (PST)
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 Gm+f9atwHyuH for <oauth@core3.amsl.com>; Mon, 30 Nov 2009 13:53:22 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 52EB23A69B8 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:53:21 -0800 (PST)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id nAULrCMP008081 for <oauth@ietf.org>; Mon, 30 Nov 2009 21:53:12 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1259617993; bh=Da6cL/+iwEUVN8anhXlmbiUirfY=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=D+7KrZimNF9EnLW3cni2phM8AHut9ZPvoUPP3oM57q6KDQrx+8iDvs0AJyUlR3Z4m hINoeyAA1DcicGzVOAB3w==
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=uDisRta/FjVGMGh4mHQDa6SeFsKkAH/8WhrvfzuPXuB9Yewf7Gt+Rs/ctqUPghjCo 8n8G722Mn0NzVw7C+jB6Q==
Received: from pzk14 (pzk14.prod.google.com [10.243.19.142]) by wpaz13.hot.corp.google.com with ESMTP id nAULr0dW009038 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:53:10 -0800
Received: by pzk14 with SMTP id 14so2855490pzk.23 for <oauth@ietf.org>; Mon, 30 Nov 2009 13:53:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.4.12 with SMTP id g12mr322860rvi.189.1259617989594; Mon, 30 Nov 2009 13:53:09 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343785209B82@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <90C41DD21FB7C64BB94121FBBC2E72343785209A24@P3PW5EX1MB01.EX1.SECURESERVER.NET> <1259536078.19069.6.camel@localhost> <90C41DD21FB7C64BB94121FBBC2E72343785209A5A@P3PW5EX1MB01.EX1.SECURESERVER.NET> <ED97F89464499E4D80A68CDCE1E3D1FF020897A1@PACORPEXCMB03.cable.comcast.com> <90C41DD21FB7C64BB94121FBBC2E72343785209B82@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 30 Nov 2009 13:53:09 -0800
Message-ID: <daf5b9570911301353r54e8690dv1d87de8e32675db9@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: "Moore, Jonathan (CIM)" <Jonathan_Moore@comcast.com>, "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] keeping support for RSA (Was: RE: OAuth 2.0 / Charter)
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: Mon, 30 Nov 2009 21:53:23 -0000

On Mon, Nov 30, 2009 at 11:25 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
>
> 4. We are still very likely to have a PK-based method for obtaining *authorization* (a token). So
> PK will be still available for obtaining a token. I know this does not address the 2-legged
> scenario, but whatever we come up there should be the same with whatever we may end
> up including in the authentication part.

This does actually address the two-legged scenario quite nicely.

Client sends PK-signed message to Authorization Server.
Authorization Server returns token.
Client uses token.

Cheers,
Brian

v2.23.0 | Report a Bug | By Email