Re: [OAUTH-WG] Issue: add refresh token as optional in all access token requests

Richard Barnes <rbarnes@bbn.com> Fri, 16 April 2010 16:08 UTC

Return-Path: <rbarnes@bbn.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 0A89C3A68ED for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 09:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level:
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599]
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 5tGkKzfFFrpg for <oauth@core3.amsl.com>; Fri, 16 Apr 2010 09:08:09 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id BDA5228C1CE for <oauth@ietf.org>; Fri, 16 Apr 2010 09:08:07 -0700 (PDT)
Received: from [192.1.255.202] (port=52287 helo=col-dhcp-192-1-255-202.bbn.com) by smtp.bbn.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1O2o5I-0001Ti-9A; Fri, 16 Apr 2010 12:08:00 -0400
Message-Id: <F74CD1E6-8B47-4F42-8E08-6F31CB6174B5@bbn.com>
From: Richard Barnes <rbarnes@bbn.com>
To: David Recordon <recordond@gmail.com>
In-Reply-To: <h2sfd6741651004151222of48b86c7pedd36f9d653d607e@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 16 Apr 2010 12:08:00 -0400
References: <C7ECB32C.3235C%eran@hueniverse.com> <h2sfd6741651004151222of48b86c7pedd36f9d653d607e@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Issue: add refresh token as optional in all access token requests
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: Fri, 16 Apr 2010 16:08:10 -0000

Sure, this seems sensible, especially with the *optional* part.



On Apr 15, 2010, at 3:22 PM, David Recordon wrote:

> +1, remember discussing this a week or so ago on the list
>
> On Thu, Apr 15, 2010 at 12:12 PM, Eran Hammer-Lahav <eran@hueniverse.com 
> > wrote:
>> Not all the flows return a refresh token for security or practicality
>> reasons. Adding refresh token as optional in all access token  
>> requests is
>> required to enable upgrading a token to a token with secret. It  
>> also can
>> make the spec slightly shorter by not having to repeat all the  
>> parameters.
>>
>> We need to either add it to every token response or allow the  
>> client to
>> request a secret directly without having to refresh the token.
>>
>> Proposal: Keep bearer tokens as the default first-issued credential  
>> and add
>> an optional refresh token everywhere.
>>
>> EHL
>>
>> _______________________________________________
>> 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