Re: [OAUTH-WG] best practices for storing access token for implicit clients
Marius Scurtescu <mscurtescu@google.com> Mon, 11 July 2011 22:15 UTC
Return-Path: <mscurtescu@google.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE6E11E831B for <oauth@ietfa.amsl.com>; Mon, 11 Jul 2011 15:15:52 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFjEyQhf8WWe for <oauth@ietfa.amsl.com>; Mon, 11 Jul 2011 15:15:51 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9AB11E831A for <oauth@ietf.org>; Mon, 11 Jul 2011 15:15:51 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id p6BMFo8o030244 for <oauth@ietf.org>; Mon, 11 Jul 2011 15:15:50 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1310422550; bh=2HWx4RH8B+QLbAWmoOP10WUWRac=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=e5F/6tBSj+BTTDZDKfd8ri7wcCB8RFt8hti0R1jCc9u5KNLciHILW6rBXYTUd8mve v22DOpP4ymjnb8ntjNUtQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=EgXzY0KZYD6rO4LRhKFWnOKMB9VHLPSv/0pkAfC8pzpbPTqW4YjkwVzRqpUQEoFcI j3pwITX01CLMWJwbCeshA==
Received: from gyh3 (gyh3.prod.google.com [10.243.50.195]) by hpaq12.eem.corp.google.com with ESMTP id p6BMFjGT014918 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Mon, 11 Jul 2011 15:15:49 -0700
Received: by gyh3 with SMTP id 3so1700520gyh.19 for <oauth@ietf.org>; Mon, 11 Jul 2011 15:15:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=MN9GL+48IhOIDTq08LTOVTpdXc/3s0Q7qk9YblHikJM=; b=iCfS3U75X6UlfVC7e9iSHpHdvPsbddxRXev+IU4k5v0Igke6AEe8fwuZ5bwnBfrZ40 QDeeE3K1kVE8VgjZ6ibQ==
Received: by 10.101.119.2 with SMTP id w2mr4194261anm.167.1310422549117; Mon, 11 Jul 2011 15:15:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.14.19 with HTTP; Mon, 11 Jul 2011 15:15:29 -0700 (PDT)
In-Reply-To: <BANLkTimU=RGHpHJTb97xvnpaqxqbc_qLhw@mail.gmail.com>
References: <BANLkTimU=RGHpHJTb97xvnpaqxqbc_qLhw@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 11 Jul 2011 15:15:29 -0700
Message-ID: <CAGdjJpLBg7-998tZm1uYQ2brsgfc7kyEr7VdF4Rd6ns+CAQGmA@mail.gmail.com>
To: Doug Tangren <d.tangren@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] best practices for storing access token for implicit clients
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 11 Jul 2011 22:15:52 -0000
On Thu, Jun 30, 2011 at 12:45 PM, Doug Tangren <d.tangren@gmail.com> wrote: > What is the current recommended practice of storing an implicit client's > access_tokens? LocalStorage, im mem and re-request auth on every browser > refresh? Both sound reasonable. I think most important is how NOT to store it, in a cookie. Marius
- [OAUTH-WG] best practices for storing access toke… Doug Tangren
- [OAUTH-WG] best practices for storing access toke… Doug Tangren
- Re: [OAUTH-WG] best practices for storing access … Marius Scurtescu
- Re: [OAUTH-WG] best practices for storing access … Eran Hammer-Lahav
- Re: [OAUTH-WG] best practices for storing access … Larry Suto
- Re: [OAUTH-WG] best practices for storing access … Ian McKellar
- Re: [OAUTH-WG] best practices for storing access … Ian McKellar
- Re: [OAUTH-WG] best practices for storing access … Doug Tangren