Re: [OAUTH-WG] in-app logout?

Chasen Le Hara <chasen@ironmoney.com> Fri, 21 May 2010 05:38 UTC

Return-Path: <chasen@ironmoney.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 80E0C3A7DEA for <oauth@core3.amsl.com>; Thu, 20 May 2010 22:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.541
X-Spam-Level:
X-Spam-Status: No, score=0.541 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 WH2bnWj3D5ZW for <oauth@core3.amsl.com>; Thu, 20 May 2010 22:38:42 -0700 (PDT)
Received: from mail-qy0-f200.google.com (mail-qy0-f200.google.com [209.85.221.200]) by core3.amsl.com (Postfix) with ESMTP id B6EC63A7E19 for <oauth@ietf.org>; Thu, 20 May 2010 21:05:30 -0700 (PDT)
Received: by qyk38 with SMTP id 38so886664qyk.17 for <oauth@ietf.org>; Thu, 20 May 2010 21:05:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.232.6 with SMTP id js6mr284470qcb.14.1274414721103; Thu, 20 May 2010 21:05:21 -0700 (PDT)
Received: by 10.229.226.8 with HTTP; Thu, 20 May 2010 21:05:21 -0700 (PDT)
In-Reply-To: <AANLkTikxD3jraqvG2IFmaSme0f1Q7NGPuQ3llqX3Ds5W@mail.gmail.com>
References: <4BEBDCFB.7090503@lodderstedt.net> <255B9BB34FB7D647A506DC292726F6E11263465727@WSMSG3153V.srv.dir.telstra.com> <AANLkTikxD3jraqvG2IFmaSme0f1Q7NGPuQ3llqX3Ds5W@mail.gmail.com>
Date: Thu, 20 May 2010 21:05:21 -0700
Message-ID: <AANLkTinnZUp5fPB6SEtFGvAT11iGtkBy_zwx1EO6sxSS@mail.gmail.com>
From: Chasen Le Hara <chasen@ironmoney.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0016363b90f6bf799c048712cc8d"
Subject: Re: [OAUTH-WG] in-app logout?
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, 21 May 2010 05:38:43 -0000

On Sun, May 16, 2010 at 11:27 AM, Dick Hardt <dick.hardt@gmail.com> wrote:

> Torsten: enabling a client to revoke a refresh token looks like a useful
> mechanism. I anticipate it will be viewed as a vitamin feature rather than a
> painkiller and will fall by the wayside unless the security conscience rally
> to have it included.
>

I’d like to put in another vote for this mechanism.

I’m about to add a “in-app logout” to an iPhone app that uses OAuth; while I
can delete the token from the device, a standard way for deleting the token
from the web service would be helpful in preventing future uses of the token
(for example, if the device is restored from a backup and the token was
stored in the backup files).
-Chasen