[OAUTH-WG] in-app logout?

Torsten Lodderstedt <torsten@lodderstedt.net> Thu, 13 May 2010 11:10 UTC

Return-Path: <torsten@lodderstedt.net>
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 B5A903A6C58 for <oauth@core3.amsl.com>; Thu, 13 May 2010 04:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level:
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[AWL=-0.701, BAYES_50=0.001, HELO_EQ_DE=0.35]
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 7Pa0hNLjdf9P for <oauth@core3.amsl.com>; Thu, 13 May 2010 04:10:00 -0700 (PDT)
Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.31.29]) by core3.amsl.com (Postfix) with ESMTP id D3D523A6CCF for <oauth@ietf.org>; Thu, 13 May 2010 04:05:44 -0700 (PDT)
Received: from p4fff22e2.dip.t-dialin.net ([79.255.34.226] helo=[127.0.0.1]) by smtprelay02.ispgateway.de with esmtpa (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1OCWEP-0002wW-NO for oauth@ietf.org; Thu, 13 May 2010 13:05:33 +0200
Message-ID: <4BEBDCFB.7090503@lodderstedt.net>
Date: Thu, 13 May 2010 13:05:31 +0200
From: Torsten Lodderstedt <torsten@lodderstedt.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-15"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Df-Sender: 141509
Subject: [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: Thu, 13 May 2010 11:10:02 -0000

OAuth currently focues on the issuance and usage of tokens.

What about refresh token revocation/deletion?

Several mobile apps today use long-living tokens as a means to log in to 
services. They typically also offer a button to log-off/log-out, which 
cause the app to delete the token from the device. From my point of 
view, it would be beneficially if the client could also discard the 
refresh token at the authorization server. Otherwise the token is still 
valid, which might be intransparent to the user.

I propose to add another request "delete" (or cancel or logoff or 
logout) which allows the client to delete the refresh token (and the 
end-user authorization it represents) at the authorization server.

Parameters: client_id, client_secret (optional), refresh_token

The request must check whether the token has been issued to the calling 
client. Otherwise the request is refused.

Thoughts?

regards,
Torsten.