Re: [OAUTH-WG] Understanding how OpenSocial uses OAuth 1.0a

Brian Eaton <beaton@google.com> Fri, 19 March 2010 18:44 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 DE8DE3A67EC for <oauth@core3.amsl.com>; Fri, 19 Mar 2010 11:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.401
X-Spam-Level:
X-Spam-Status: No, score=-105.401 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, 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 70aEu1b2rTpu for <oauth@core3.amsl.com>; Fri, 19 Mar 2010 11:44:48 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 0032F3A681B for <oauth@ietf.org>; Fri, 19 Mar 2010 11:44:47 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id o2JIj06F010333 for <oauth@ietf.org>; Fri, 19 Mar 2010 11:45:00 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1269024300; bh=GvzPDAvnrYfGLoiWNxrVnuQ50I4=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=W8x5j2+pIAYQrAq0yr1Yn4LryakVVTAVwGcxGUhz8WgvtVf6TNkm+sdOSCI3Qn4Yz hZlDOgMDZq/ck3rIQ2uRg==
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=azDpVE6l0t+YKxfD22XAWNqtv21ONOakHTusaZqEqLteHwuVT37KV6iixeMHwcemK CkFWjSgG7LSVu9fLSPKPA==
Received: from vws18 (vws18.prod.google.com [10.241.21.146]) by wpaz5.hot.corp.google.com with ESMTP id o2JIixoS000967 for <oauth@ietf.org>; Fri, 19 Mar 2010 11:45:00 -0700
Received: by vws18 with SMTP id 18so563897vws.34 for <oauth@ietf.org>; Fri, 19 Mar 2010 11:44:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.124.1 with SMTP id s1mr1900499vcr.230.1269024299528; Fri, 19 Mar 2010 11:44:59 -0700 (PDT)
In-Reply-To: <68f4a0e81003191052m7ab778d6n330e58bd58b9f924@mail.gmail.com>
References: <fd6741651003161112y2eceb494ue28db2644ba1d32a@mail.gmail.com> <68f4a0e81003191052m7ab778d6n330e58bd58b9f924@mail.gmail.com>
Date: Fri, 19 Mar 2010 11:44:59 -0700
Message-ID: <daf5b9571003191144j74ea597cgf06ef3ba449cecef@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Ethan Jewett <esjewett@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Understanding how OpenSocial uses OAuth 1.0a
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, 19 Mar 2010 18:44:49 -0000

On Fri, Mar 19, 2010 at 10:52 AM, Ethan Jewett <esjewett@gmail.com> wrote:
> If I'm reading correctly, if the gadget chooses to use the container's
> private key, then that is making use of the RSA signature mechanism.
> If the gadget chooses to use the container's shared secret, then that
> is the HMAC-SHA1 signature mechanism.

That's right.

> It looks to me like the
> PLAINTEXT method is not supported at all based on the wiki though I
> don't see a technical reason why it should not be supported.

Plaintext doesn't work in this context, because it sends long-lived
secrets in clear-text to servers that are under the control of the
application author, or, in the case of gadgets, everyone viewing the
gadget.

Cheers,
Brian