Re: [OAUTH-WG] Single transaction token
Eran Hammer-Lahav <eran@hueniverse.com> Tue, 08 November 2011 15:18 UTC
Return-Path: <eran@hueniverse.com>
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 09B2021F8C2A for <oauth@ietfa.amsl.com>; Tue, 8 Nov 2011 07:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level:
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, 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 OsLi+Bs62E0s for <oauth@ietfa.amsl.com>; Tue, 8 Nov 2011 07:18:28 -0800 (PST)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by ietfa.amsl.com (Postfix) with SMTP id 6B48221F8C1D for <oauth@ietf.org>; Tue, 8 Nov 2011 07:18:28 -0800 (PST)
Received: (qmail 10753 invoked from network); 8 Nov 2011 15:18:21 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.19) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 8 Nov 2011 15:18:21 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Tue, 8 Nov 2011 08:18:18 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Declan Newman <declan.newman@semantico.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Tue, 08 Nov 2011 08:18:13 -0700
Thread-Topic: [OAUTH-WG] Single transaction token
Thread-Index: Acyd/PA/TdXjXbX3RDyPJtrkG+i1ygALJQJw
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723452634039D7@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <C1468D5F-052D-4D14-919E-A0465156A780@semantico.com>
In-Reply-To: <C1468D5F-052D-4D14-919E-A0465156A780@semantico.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_90C41DD21FB7C64BB94121FBBC2E723452634039D7P3PW5EX1MB01E_"
MIME-Version: 1.0
Cc: Will Simpson <will.simpson@semantico.com>, Geoffrey Bilder <gbilder@crossref.org>
Subject: Re: [OAUTH-WG] Single transaction token
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: Tue, 08 Nov 2011 15:18:29 -0000
No, but you can define a new parameter for use instead or alongside the existing parameter. EHL From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Declan Newman Sent: Tuesday, November 08, 2011 1:58 AM To: oauth@ietf.org Cc: Will Simpson; Geoffrey Bilder Subject: [OAUTH-WG] Single transaction token Hello, We're currently implementing OAuth 2 provider for a client, whom needs to have the facility to authenticate/authorise a client to update in a single transaction. Is there a way to specify the validity of a token on a per-transaction basis, as opposed to a timeframe? Any help much appreciated. Regards, Dec ---------------------------------------------------------------------------- Declan Newman, Development Team Leader, Semantico, Floor 1, 21-23 Dyke Road, Brighton BN1 3FE <mailto:Declan.Newman@semantico.com> <tel:+44-1273-358247>
- [OAUTH-WG] Single transaction token Declan Newman
- Re: [OAUTH-WG] Single transaction token Eran Hammer-Lahav
- Re: [OAUTH-WG] Single transaction token William Mills
- Re: [OAUTH-WG] Single transaction token Declan Newman
- Re: [OAUTH-WG] Single transaction token William Mills