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

"Richer, Justin P." <> Tue, 17 January 2012 18:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9D6E511E80AA; Tue, 17 Jan 2012 10:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bsfSGdD9w8Lk; Tue, 17 Jan 2012 10:59:31 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 82E8D11E80A6; Tue, 17 Jan 2012 10:59:31 -0800 (PST)
Received: from (localhost.localdomain []) by localhost (Postfix) with SMTP id F25D721B17B3; Tue, 17 Jan 2012 13:59:30 -0500 (EST)
Received: from IMCCAS01.MITRE.ORG ( []) by (Postfix) with ESMTP id DDA4421B17A5; Tue, 17 Jan 2012 13:59:30 -0500 (EST)
Received: from IMCMBX01.MITRE.ORG ([]) by IMCCAS01.MITRE.ORG ([]) with mapi id 14.01.0339.001; Tue, 17 Jan 2012 13:59:30 -0500
From: "Richer, Justin P." <>
To: Torsten Lodderstedt <>, Paul Madsen <>
Thread-Topic: AW: Re: [OAUTH-WG] Access Token Response without expires_in
Thread-Index: AczUf8kvUkdgy1nHSGOm5KixWQExDAAclWSAABTAkIAABtE5gAAAVTyAAAFYhID//8HxSQ==
Date: Tue, 17 Jan 2012 18:59:30 +0000
Message-ID: <B33BFB58CCC8BE4998958016839DE27E09EC78@IMCMBX01.MITRE.ORG>
References: <90C41DD21FB7C64BB94121FBBC2E723453A754C549@P3PW5EX1MB01.EX1.SECURESERVER.NET> <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B33BFB58CCC8BE4998958016839DE27E09EC78IMCMBX01MITREORG_"
MIME-Version: 1.0
Cc: "" <>, OAuth WG <>
Subject: Re: [OAUTH-WG] Access Token Response without expires_in
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Jan 2012 18:59:32 -0000

By the same argument, the client can know how long the tokens are good for via API description. What we're talking about is a programmatic hint by the AS to the Client about what the token is good for. One common use is time-limited, and so provisions for that have been baked in so that everybody does it the same way. If there's enough out there to be use-limited or other bits, we should have a tiny provision to extend this in a similar fashion.

 -- Justin

From: Torsten Lodderstedt []
Sent: Tuesday, January 17, 2012 12:26 PM
To: Paul Madsen
Cc:; 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.


Paul Madsen <> 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?


On 1/17/12 11:38 AM,<> wrote:


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?

Gesendet mit BlackBerry® Webmail von Telekom Deutschland

-----Original Message-----
From: Paul Madsen <><>
Date: Tue, 17 Jan 2012 08:23:37
To: Richer, Justin P.<><>
Cc: OAuth WG<><>
Subject: Re: [OAUTH-WG] Access Token Response without expires_in

OAuth mailing list<>