IETF Logo Mail Archive

Re: [OAUTH-WG] Refresh tokens

Phil Hunt <phil.hunt@oracle.com> Wed, 15 June 2011 21:01 UTC

Return-Path: <phil.hunt@oracle.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 DF16E21F851D for <oauth@ietfa.amsl.com>; Wed, 15 Jun 2011 14:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZZqGXA4BL2o for <oauth@ietfa.amsl.com>; Wed, 15 Jun 2011 14:01:48 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by ietfa.amsl.com (Postfix) with ESMTP id AAD4021F849C for <oauth@ietf.org>; Wed, 15 Jun 2011 14:01:48 -0700 (PDT)
Received: from rtcsinet21.oracle.com (rtcsinet21.oracle.com [66.248.204.29]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p5FL1is6028224 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Jun 2011 21:01:46 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by rtcsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id p5FL1hRK021068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jun 2011 21:01:44 GMT
Received: from abhmt001.oracle.com (abhmt001.oracle.com [141.146.116.10]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id p5FL1cgZ004489; Wed, 15 Jun 2011 16:01:38 -0500
Received: from dhcp-2op4-5-west-130-35-46-25.usdhcp.oraclecorp.com (/130.35.46.25) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 15 Jun 2011 14:01:37 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary="Apple-Mail-20--847979276"
From: Phil Hunt <phil.hunt@oracle.com>
In-Reply-To: <BANLkTi=-4rhzTP-wF2GowSrDyBRAXsnD1bN3uFM3XOSerf1Ddw@mail.gmail.com>
Date: Wed, 15 Jun 2011 14:01:42 -0700
Message-Id: <84547248-0D7A-4F85-B501-2196B7DF4716@oracle.com>
References: <90C41DD21FB7C64BB94121FBBC2E7234475E986AF9@P3PW5EX1MB01.EX1.SECURESERVER.NET> <BANLkTimVQL=4O3=L+et1XSx7-=h4Jnwd+g68siNqpMbSMn_wjA@mail.gmail.com> <1308169456.72680.YahooMailNeo@web31810.mail.mud.yahoo.com> <BANLkTi=-4rhzTP-wF2GowSrDyBRAXsnD1bN3uFM3XOSerf1Ddw@mail.gmail.com>
To: Brian Eaton <beaton@google.com>
X-Mailer: Apple Mail (2.1084)
X-Source-IP: rtcsinet21.oracle.com [66.248.204.29]
X-CT-RefId: str=0001.0A090205.4DF91DBB.00CA:SCFSTAT5015188,ss=1,fgs=0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Refresh tokens
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, 15 Jun 2011 21:01:50 -0000

+ 1

Phil

@independentid
www.independentid.com
phil.hunt@oracle.com





On 2011-06-15, at 1:39 PM, Brian Eaton wrote:

> Yeah, I agree with that change.
> 
> On Wed, Jun 15, 2011 at 1:24 PM, William J. Mills <wmills@yahoo-inc.com> wrote:
> I like your draft in general, but 
> 
>      10.1.3. Access Tokens
> 
>      Access tokens are shorter-lived versions of refresh tokens.
> 
> Doesn't work for me.  Access tokens are credentials used to access protected resources.  Refresh 
> 
> tokens are credentials used to obtain access tokens.
> 
> -bill
> 
> From: Brian Eaton <beaton@google.com>
> To: Eran Hammer-Lahav <eran@hueniverse.com>
> Cc: OAuth WG <oauth@ietf.org>
> Sent: Wednesday, June 15, 2011 11:32 AM
> 
> Subject: Re: [OAUTH-WG] Refresh tokens
> 
> On Wed, Jun 15, 2011 at 10:30 AM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> I would like to add a quick discussion of access token and refresh token recommended deployment setup, providing clear guidelines when a refresh token SHOULD and SHOULD NOT be issued, and when issues, how it is difference from the access token.
> 
> Is this a start?
> 
> http://www.ietf.org/mail-archive/web/oauth/current/msg06362.html
>   
> It’s time we stop trying to accommodate every possible combination and make some hard choices.
> 
> +1.  Yes please.
> 
> _______________________________________________
> 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

v2.23.0 | Report a Bug | By Email