IETF Logo Mail Archive

Re: [OAUTH-WG] best practices for storing access token for implicit clients

Eran Hammer-Lahav <eran@hueniverse.com> Mon, 11 July 2011 22:47 UTC

Return-Path: <eran@hueniverse.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 88DD311E8312 for <oauth@ietfa.amsl.com>; Mon, 11 Jul 2011 15:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599]
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 ngP9R8+4P7Ay for <oauth@ietfa.amsl.com>; Mon, 11 Jul 2011 15:47:35 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by ietfa.amsl.com (Postfix) with SMTP id E7A9F11E80F4 for <oauth@ietf.org>; Mon, 11 Jul 2011 15:47:34 -0700 (PDT)
Received: (qmail 21388 invoked from network); 11 Jul 2011 22:47:34 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 11 Jul 2011 22:47:34 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Mon, 11 Jul 2011 15:46:59 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Marius Scurtescu <mscurtescu@google.com>, Doug Tangren <d.tangren@gmail.com>
Date: Mon, 11 Jul 2011 15:46:50 -0700
Thread-Topic: [OAUTH-WG] best practices for storing access token for implicit clients
Thread-Index: AcxAGEHUANytKntTQrqtPHUg/wPQAQABAonw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E7234501D4A042D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <BANLkTimU=RGHpHJTb97xvnpaqxqbc_qLhw@mail.gmail.com> <CAGdjJpLBg7-998tZm1uYQ2brsgfc7kyEr7VdF4Rd6ns+CAQGmA@mail.gmail.com>
In-Reply-To: <CAGdjJpLBg7-998tZm1uYQ2brsgfc7kyEr7VdF4Rd6ns+CAQGmA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "oauth@ietf.org" <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:47:35 -0000

Any cookie? What about a Secure cookie limited to a specific sub-domain? What are the concerns about cookies? I think this would be helpful to discuss.

EHL

> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Marius Scurtescu
> Sent: Monday, July 11, 2011 3:15 PM
> To: Doug Tangren
> Cc: oauth@ietf.org
> Subject: Re: [OAUTH-WG] best practices for storing access token for implicit
> clients
> 
> 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 mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.36.0 | Report a Bug | By Email | System Status