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

Allen Tom <atom@yahoo-inc.com> Fri, 21 May 2010 19:36 UTC

Return-Path: <atom@yahoo-inc.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 31F403A6899 for <oauth@core3.amsl.com>; Fri, 21 May 2010 12:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.073
X-Spam-Level:
X-Spam-Status: No, score=-14.073 tagged_above=-999 required=5 tests=[AWL=-0.805, BAYES_50=0.001, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396, USER_IN_DEF_WHITELIST=-15]
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 rXUxuD1ibXDf for <oauth@core3.amsl.com>; Fri, 21 May 2010 12:36:40 -0700 (PDT)
Received: from mrout1-b.corp.re1.yahoo.com (mrout1-b.corp.re1.yahoo.com [69.147.107.20]) by core3.amsl.com (Postfix) with ESMTP id 694243A6EAD for <oauth@ietf.org>; Fri, 21 May 2010 09:18:11 -0700 (PDT)
Received: from SNV-EXBH01.ds.corp.yahoo.com (snv-exbh01.ds.corp.yahoo.com [207.126.227.249]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id o4LFlRsE029543; Fri, 21 May 2010 08:47:29 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=received:user-agent:date:subject:from:to:message-id: thread-topic:thread-index:in-reply-to:mime-version:content-type: return-path:x-originalarrivaltime; b=JmbQDLlW1i9WvW0Vdl/DzI8/yjl0QN/Khe4n4pNqAgJjo7KgXBwCttpHI13azyjY
Received: from SNV-EXVS03.ds.corp.yahoo.com ([207.126.227.235]) by SNV-EXBH01.ds.corp.yahoo.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 21 May 2010 08:47:27 -0700
Received: from 10.72.245.19 ([10.72.245.19]) by SNV-EXVS03.ds.corp.yahoo.com ([207.126.227.239]) via Exchange Front-End Server snv-webmail.corp.yahoo.com ([207.126.227.59]) with Microsoft Exchange Server HTTP-DAV ; Fri, 21 May 2010 15:47:20 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 21 May 2010 08:47:20 -0700
From: Allen Tom <atom@yahoo-inc.com>
To: Chasen Le Hara <chasen@ironmoney.com>, OAuth WG <oauth@ietf.org>
Message-ID: <C81BF918.308DE%atom@yahoo-inc.com>
Thread-Topic: [OAUTH-WG] in-app logout?
Thread-Index: Acr4/OWKYROV68v5IU+kME9p3XlFPg==
In-Reply-To: <AANLkTinnZUp5fPB6SEtFGvAT11iGtkBy_zwx1EO6sxSS@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3357276441_35861805"
X-OriginalArrivalTime: 21 May 2010 15:47:27.0920 (UTC) FILETIME=[EA433300:01CAF8FC]
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 19:36:43 -0000

+1

There are many examples in production of token authentication schemes that
have a ³revoke token² API for clients to voluntarily revoke their own
credentials.  

Examples:

Google¹s AuthSubRevokeToken:
http://code.google.com/apis/accounts/docs/AuthSub.html#AuthSubRevokeToken

OAuth Session Extension (for OAuth 1.0a):
http://oauth.googlecode.com/svn/spec/ext/session/1.0/drafts/1/spec.html#anch
or10

Allen

On 5/20/10 9:05 PM, "Chasen Le Hara" <chasen@ironmoney.com> wrote:

> 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
> 
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth