Re: [OAUTH-WG] Access Token Response without expires_in

Torsten Lodderstedt <torsten@lodderstedt.net> Wed, 18 January 2012 06:48 UTC

Return-Path: <torsten@lodderstedt.net>
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 EB26421F8743; Tue, 17 Jan 2012 22:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jhy7mE5rdxh9; Tue, 17 Jan 2012 22:48:49 -0800 (PST)
Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id D736121F8741; Tue, 17 Jan 2012 22:48:48 -0800 (PST)
Received: from [79.253.33.127] (helo=[192.168.71.31]) by smtprelay03.ispgateway.de with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1RnPK9-0007m6-Mb; Wed, 18 Jan 2012 07:48:45 +0100
References: <90C41DD21FB7C64BB94121FBBC2E723453A754C549@P3PW5EX1MB01.EX1.SECURESERVER.NET> <E4309A9E-9BC7-4547-918A-224B6233B25C@mitre.org> <4F157659.7050701@gmail.com> <1451834425-1326818330-cardhu_decombobulator_blackberry.rim.net-253428785-@b4.c11.bise7.blackberry> <4F15A655.4060404@gmail.com>, <2fc6806a-8a15-4b97-87f2-3c0c0cbd3623@email.android.com> <B33BFB58CCC8BE4998958016839DE27E09EC78@IMCMBX01.MITRE.ORG> <1326833912.76041.YahooMailNeo@web31813.mail.mud.yahoo.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <1326833912.76041.YahooMailNeo@web31813.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----81UE611OHB02WT6BYGCLNA1LEMS9JM"
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Date: Wed, 18 Jan 2012 07:48:28 +0100
To: William Mills <wmills@yahoo-inc.com>, "Richer, Justin P." <jricher@mitre.org>, Paul Madsen <paul.madsen@gmail.com>
Message-ID: <d53e8d6e-6d37-4747-b2cd-eb40752e93bc@email.android.com>
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Access Token Response without expires_in
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: Wed, 18 Jan 2012 06:48:50 -0000

good point



William Mills <wmills@yahoo-inc.com> schrieb:


One use tokens can also expire before they are used.  "You have 5 minutes to do this once."

_____________________________________________

From: Torsten Lodderstedt [torsten@lodderstedt.net]
Sent: Tuesday, January 17, 2012 12:26 PM
To: Paul Madsen
Cc: oauth-bounces@ietf.org; Richer, Justin P.; OAuth WG
Subject: Re: AW: Re: [OAUTH-WG] Access Token Response without expires_in

Hi Paul,

that's not what I meant. The Client should know which tokens should be one time usage based on the API description. The authz server must not return expires_in because this would not make any sense in this case.

regards,
Torsten




Paul Madsen <paul.madsen@gmail.com> schrieb: 

Hi Torsten, yes the use case in question is payment-based as well. 

Your suggestion for the client to infer one-time usage from a missing expires_in contradicts the general consensus of this thread does it not?

paul

On 1/17/12 11:38 AM, torsten@lodderstedt.net wrote: 

Hi, isn't one-time semantics typically associated with certain requests on certain resources/resource types. I therefore would assume the client to know which tokens to use one-time only. The authz server should not return an expires_in paramter. We for example use one time access tokens for payment transactions. What would such an extension specify? regards, Torsten. Gesendet mit BlackBerry® Webmail von Telekom Deutschland -----Original Message----- From: Paul Madsen <paul.madsen@gmail.com> Sender: oauth-bounces@ietf.org Date: Tue, 17 Jan 2012 08:23:37 To: Richer, Justin P.<jricher@mitre.org> Cc: OAuth WG<oauth@ietf.org> Subject: Re: [OAUTH-WG] Access Token Response without expires_in _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth 


_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth