Re: [OAUTH-WG] Token expiration
Chris Messina <chris.messina@gmail.com> Mon, 21 September 2009 22:21 UTC
Return-Path: <chris.messina@gmail.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 244AD3A6866 for <oauth@core3.amsl.com>; Mon, 21 Sep 2009 15:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 YThnpd-FADry for <oauth@core3.amsl.com>; Mon, 21 Sep 2009 15:21:14 -0700 (PDT)
Received: from mail-vw0-f196.google.com (mail-vw0-f196.google.com [209.85.212.196]) by core3.amsl.com (Postfix) with ESMTP id D19E53A680A for <oauth@ietf.org>; Mon, 21 Sep 2009 15:21:13 -0700 (PDT)
Received: by vws34 with SMTP id 34so2282042vws.32 for <oauth@ietf.org>; Mon, 21 Sep 2009 15:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=OcsptvBkfJ+98MR+YBHpqDHNx+nr+wtCT9w+szM2DfY=; b=U+WCISvxkq9U0y99ZbryoD7hgi4VxxtpzpkLDUqGM+BL6NYj5XxEnKYxfBtFovEkCX jjdbwSOoDs5E6RX+G450y0JDyfKHSRXSLLK8Vt6QV+NDkZLI0C4TMryjeS1xGOvnZaJO kkctflkTB+bsEcx30ybX3z6evsmqnRHhmA7FM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=P7JqqKYc0TRcDSvTvnQz+0UTdZoQ9fNYW42jzRU4vbUES1fWjSKQ/UcoZsswsDPW8a XcTywnKMcoP0Wkn01cfRyYkTXEbfXwioNpG9yKwtF9uZCyFR3F5PLC3Rd6r87vs1Cii6 Fgcciq3ycWlwxOoIoFb8TUAGcJklnltWBwNrI=
MIME-Version: 1.0
Received: by 10.220.88.23 with SMTP id y23mr289140vcl.94.1253571732903; Mon, 21 Sep 2009 15:22:12 -0700 (PDT)
In-Reply-To: <6c0fd2bc0909211441o3eacc564t2917cf5b94f99800@mail.gmail.com>
References: <90C41DD21FB7C64BB94121FBBC2E72343784D584A3@P3PW5EX1MB01.EX1.SECURESERVER.NET> <6c0fd2bc0909211441o3eacc564t2917cf5b94f99800@mail.gmail.com>
Date: Mon, 21 Sep 2009 15:22:12 -0700
Message-ID: <1bc4603e0909211522h2f659866v48ff9dcee9294b7a@mail.gmail.com>
From: Chris Messina <chris.messina@gmail.com>
To: Hubert Le Van Gong <hubertlvg@gmail.com>
Content-Type: multipart/alternative; boundary="0016e64602a6d719e404741de953"
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:21:15 -0000
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-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