IETF Logo Mail Archive

Re: [OAUTH-WG] Refresh token security considerations

"William J. Mills" <wmills@yahoo-inc.com> Tue, 12 July 2011 15:29 UTC

Return-Path: <wmills@yahoo-inc.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 65A8521F8EB3 for <oauth@ietfa.amsl.com>; Tue, 12 Jul 2011 08:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.226
X-Spam-Level:
X-Spam-Status: No, score=-17.226 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15]
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 VY4Q8+j3dijg for <oauth@ietfa.amsl.com>; Tue, 12 Jul 2011 08:29:32 -0700 (PDT)
Received: from nm11.bullet.mail.bf1.yahoo.com (nm11.bullet.mail.bf1.yahoo.com [98.139.212.170]) by ietfa.amsl.com (Postfix) with SMTP id 61EC921F8EB2 for <oauth@ietf.org>; Tue, 12 Jul 2011 08:29:32 -0700 (PDT)
Received: from [98.139.212.152] by nm11.bullet.mail.bf1.yahoo.com with NNFMP; 12 Jul 2011 15:29:29 -0000
Received: from [98.139.212.198] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 12 Jul 2011 15:29:29 -0000
Received: from [127.0.0.1] by omp1007.mail.bf1.yahoo.com with NNFMP; 12 Jul 2011 15:29:29 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 329058.28035.bm@omp1007.mail.bf1.yahoo.com
Received: (qmail 94127 invoked by uid 60001); 12 Jul 2011 15:29:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1310484568; bh=p+UxIFwF9YX7gzfVTx7R+NNrWzk6jVQg0Ttj/cPmdW8=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=h8NB3iafPabdaiNXLAIxwzVgQjonRJyukkr8uoj33NJY+OuxnFpDICAdTCZe2drIZvPqYwHTaJdnqhH4Upea1jGYBGDqJrEHgFIx+EKwHkJXCHkTikfe8XjVKciYjpmr/ddq9ucQDeVwdbw9foBo7jHtO2O2fLQSGdJg45Yal8g=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Owp37HTyVWY3ByG4DNUIDJHbi9wOu5ymKGEij5ptC9VATp61FmC2LBSwVwLa4F51iRhdOYb3KyyJthsu5RvySzJcngjD4gl4Y2YOtUNTPGpDE+S84LyquQaYEMv+vv0CQUj/ML6vYOqkvi1fKOlhgpq66gGaEhclcrSHylPTUDY=;
X-YMail-OSG: FJ4pfEUVM1mVnLVc6ufHqmiP1zByvdS6fosZv8N1IId_5lT n4in.SAKW6P3qIoLsiByd3uPaTFW9q8BEBidGaEpdbnrylupAoIaxA0V9H0X csOVsVP2EAnRspxi2_4j9GZDlsJfH0o.S3anI2OiLKCKbMMfitfKbBULE_cM ujv_79YXMk8JMWWf_y7x37GlUdZfY4XZHBZn9hKboC1FOyp7nnhdIH9dfjEO ldELRlPnRDd1yz3bgyCnp7BYsv6M30YqD2XZyqL.fZ9AuSkuZXgVEdKWy0x2 Z6o_D36ErIUKb8lxVIIcaphDJ3Ume2xSw77NbgYtgyu7QD.ibbnry0WRn_AR 9ldFNbtX3wvnN2ORGSGos
Received: from [99.31.212.42] by web31808.mail.mud.yahoo.com via HTTP; Tue, 12 Jul 2011 08:29:28 PDT
X-RocketYMMF: william_john_mills
X-Mailer: YahooMailWebService/0.8.113.313619
References: <90C41DD21FB7C64BB94121FBBC2E7234501D4A005B@P3PW5EX1MB01.EX1.SECURESERVER.NET> <152fee05-9248-45e5-a9b5-86e880e5b1f9@email.android.com> <1310315898.93782.YahooMailNeo@web31802.mail.mud.yahoo.com> <6bb0fea2-48e6-4c70-93a4-ba4528a0f9b8@email.android.com>
Message-ID: <1310484568.80888.YahooMailNeo@web31808.mail.mud.yahoo.com>
Date: Tue, 12 Jul 2011 08:29:28 -0700
From: "William J. Mills" <wmills@yahoo-inc.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>, Eran Hammer-Lahav <eran@hueniverse.com>, OAuth WG <oauth@ietf.org>
In-Reply-To: <6bb0fea2-48e6-4c70-93a4-ba4528a0f9b8@email.android.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-223830119-1310484568=:80888"
Subject: Re: [OAUTH-WG] Refresh token security considerations
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "William J. Mills" <wmills@yahoo-inc.com>
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, 12 Jul 2011 15:29:33 -0000

Why would you re-issue a refresh token every usage?  What's the use case where this makes sense?

The way I always think about the design is that refresh tokens are indended to be multi-use.  



________________________________
From: Torsten Lodderstedt <torsten@lodderstedt.net>
To: William J. Mills <wmills@yahoo-inc.com>; Eran Hammer-Lahav <eran@hueniverse.com>; OAuth WG <oauth@ietf.org>
Sent: Tuesday, July 12, 2011 12:53 AM
Subject: Re: [OAUTH-WG] Refresh token security considerations


Why?




"William J. Mills" <wmills@yahoo-inc.com> schrieb:
I agree that this is something you could do, but it doesn't seem like a good design pattern.
>
>
>
>
>________________________________
>From: Torsten Lodderstedt <torsten@lodderstedt.net>
>To: Eran Hammer-Lahav <eran@hueniverse.com>; OAuth WG <oauth@ietf.org>
>Sent: Sunday, July 10, 2011 1:21 AM
>Subject: Re: [OAUTH-WG] Refresh token security considerations
>
>replacement of the refresh token with every access token refresh is an example. The authz server creates and returns a new refresh token value with every access token refreshment. The old value is invalidated and must not be used any further. Note: The authz server keeps track of all old (invalidated) refresh tokens.
>
>If a client presents one of those old refresh tokens, the legitimate client has been compromised most likely. The authz then revokes the refresh token and the associated access authorization.
>
>regards,
>Torsten.
>
>
>
>
>Eran Hammer-Lahav <eran@hueniverse.com> schrieb:
>“the authorization server SHOULD deploy other means to detect refresh token abuse”
>> 
>>This requires an example. 
>> 
>> 
>>EHL
>_______________________________________________
>OAuth mailing list
>OAuth@ietf.org
>https://www.ietf.org/mailman/listinfo/oauth
>
>
>

v2.35.0 | Report a Bug | By Email | System Status