Re: [OAUTH-WG] Token expiration
Jonathan Sergent <sergent@google.com> Mon, 21 September 2009 22:46 UTC
Return-Path: <sergent@google.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 D11F33A6AD7 for <oauth@core3.amsl.com>; Mon, 21 Sep 2009 15:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 APQI0v9jW0+w for <oauth@core3.amsl.com>; Mon, 21 Sep 2009 15:46:53 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 793373A6982 for <oauth@ietf.org>; Mon, 21 Sep 2009 15:46:53 -0700 (PDT)
Received: from spaceape10.eur.corp.google.com (spaceape10.eur.corp.google.com [172.28.16.144]) by smtp-out.google.com with ESMTP id n8LMlrRZ018019 for <oauth@ietf.org>; Mon, 21 Sep 2009 23:47:53 +0100
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1253573273; bh=ydMozvcoIGCOZXj3l7Crp9zPnoI=; h=DomainKey-Signature:MIME-Version:In-Reply-To:References:Date: Message-ID:Subject:From:To:Cc:Content-Type: Content-Transfer-Encoding:X-System-Of-Record; b=KhwAannO/lO6h/44Bh /ZaeBn3MYM6ogS8TVM/rqvT6T2TKHWyNgC5KqrykUtXb9Pz6u136V+1UrEupS5x0wW5 w==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=g1iTO2IpZ85J9yAMKSl5dK94fO+kUzgaCEI7t3hMy9JYi+xptzu3yRgINqBAy+l39 +fPiW4YUo25j40vTVIONQ==
Received: from pxi33 (pxi33.prod.google.com [10.243.27.33]) by spaceape10.eur.corp.google.com with ESMTP id n8LMk5WU017795 for <oauth@ietf.org>; Mon, 21 Sep 2009 15:47:51 -0700
Received: by pxi33 with SMTP id 33so2740414pxi.28 for <oauth@ietf.org>; Mon, 21 Sep 2009 15:47:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.25.36 with SMTP id c36mr14448wfj.1.1253573270869; Mon, 21 Sep 2009 15:47:50 -0700 (PDT)
In-Reply-To: <6c0fd2bc0909211534s1f2b79c6m7577dee31accf9c7@mail.gmail.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343784D584A3@P3PW5EX1MB01.EX1.SECURESERVER.NET> <6c0fd2bc0909211441o3eacc564t2917cf5b94f99800@mail.gmail.com> <1bc4603e0909211522h2f659866v48ff9dcee9294b7a@mail.gmail.com> <6c0fd2bc0909211534s1f2b79c6m7577dee31accf9c7@mail.gmail.com>
Date: Mon, 21 Sep 2009 15:47:50 -0700
Message-ID: <adb0b2880909211547sd75fddfjdb2e9d31d2e825d4@mail.gmail.com>
From: Jonathan Sergent <sergent@google.com>
To: Hubert Le Van Gong <hubertlvg@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Token expiration
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: Mon, 21 Sep 2009 22:46:54 -0000
IMO, it's problematic that this relies on clock synchronization between the sender and the receiver to work. This is a constant source of problems in need of debugging for us today. Why not specify times like this using intervals? "This token is valid for the next n seconds." On Mon, Sep 21, 2009 at 3:34 PM, Hubert Le Van Gong <hubertlvg@gmail.com> wrote: > An interesting example (to me at least since we use it) is the SAML token. > You have the ability to define three dates: > - IssueInstant: the time of issue of the token [required] > - NotBefore: time before which the token's invalid [optional] > - NotOnOrAfter: time after which the token becomes invalid [optional] > > All are dateTime (in UTC form). > > Thanks, > Hubert > > > On Tue, Sep 22, 2009 at 12:22 AM, Chris Messina <chris.messina@gmail.com> wrote: >> Seems like it'd be worth documenting existing approaches to this... what do >> other similar APIs do? >> I know I harp on this approach to technology development, but that was how >> OAuth was developed (for better or worse): by looking at existing practices, >> extracting convention, and codifying ]ideally] best practices. >> If this is common and working elsewhere, can't we just imitate it? >> Chris >> >> On Mon, Sep 21, 2009 at 2:41 PM, Hubert Le Van Gong <hubertlvg@gmail.com> >> wrote: >>> >>> It is obviously useful to have. In fact it's so useful I'll bet most >>> token format >>> used do include one. Having it outside the token becomes redundant then >>> but >>> maybe it's not that bad. >>> >>> BTW why not using dateTime (http://www.w3.org/TR/xmlschema-2/#dateTime)? >>> >>> Cheers, >>> Hubert >>> >>> >>> On Mon, Sep 21, 2009 at 11:25 PM, Eran Hammer-Lahav <eran@hueniverse.com> >>> wrote: >>> > Should the core spec support the ability to indicate the duration of >>> > token credentials? This would be an addition to the web delegation draft [1] >>> > in section 6 (Token Credentials) in the form of a new response parameter, >>> > something like: >>> > >>> > oauth_token_duration >>> > The token duration specified in second from the time of the HTTP >>> > response timestamp. >>> > >>> > This has been consistently at the top of missing core funcationality. >>> > >>> > >>> > EHL >>> > >>> > [1] http://tools.ietf.org/html/draft-ietf-oauth-web-delegation-01 >>> > >>> > _______________________________________________ >>> > 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 >> >> >> >> -- >> Chris Messina >> Open Web Advocate >> >> Personal: http://factoryjoe.com >> Follow me on Twitter: http://twitter.com/chrismessina >> >> Citizen Agency: http://citizenagency.com >> Diso Project: http://diso-project.org >> OpenID Foundation: http://openid.net >> >> This email is: [ ] shareable [X] ask first [ ] private >> > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] Token expiration Eran Hammer-Lahav
- Re: [OAUTH-WG] Token expiration Hubert Le Van Gong
- Re: [OAUTH-WG] Token expiration Chris Messina
- Re: [OAUTH-WG] Token expiration Hubert Le Van Gong
- Re: [OAUTH-WG] Token expiration Jonathan Sergent
- Re: [OAUTH-WG] Token expiration Marcel Molina
- Re: [OAUTH-WG] Token expiration Hubert Le Van Gong
- Re: [OAUTH-WG] Token expiration Eran Hammer-Lahav
- Re: [OAUTH-WG] Token expiration Jonathan Sergent
- Re: [OAUTH-WG] Token expiration Chris Messina