Re: [OAUTH-WG] Multiple access tokens
Torsten Lodderstedt <torsten@lodderstedt.net> Thu, 08 March 2012 07:01 UTC
Return-Path: <torsten@lodderstedt.net>
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 87FE721F861A for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 23:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKRFAcCu7mi6 for <oauth@ietfa.amsl.com>; Wed, 7 Mar 2012 23:01:21 -0800 (PST)
Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.38]) by ietfa.amsl.com (Postfix) with ESMTP id 7D01A21F8604 for <oauth@ietf.org>; Wed, 7 Mar 2012 23:01:20 -0800 (PST)
Received: from [80.187.106.181] (helo=[31.243.207.121]) by smtprelay04.ispgateway.de with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68) (envelope-from <torsten@lodderstedt.net>) id 1S5XLi-0002i8-Pq; Thu, 08 Mar 2012 08:01:19 +0100
References: <FF6EB619-5D3E-4B94-A322-D64BD596E015@gmail.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <FF6EB619-5D3E-4B94-A322-D64BD596E015@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Date: Thu, 08 Mar 2012 08:01:02 +0100
To: Ross Boucher <rboucher@gmail.com>, OAuth WG <oauth@ietf.org>
Message-ID: <a89a082f-70ab-427e-a2c7-5eaf75d18618@email.android.com>
X-Df-Sender: dG9yc3RlbkBsb2RkZXJzdGVkdC1vbmxpbmUuZGU=
Subject: Re: [OAUTH-WG] Multiple access 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: Thu, 08 Mar 2012 07:01:22 -0000
Hi, Ross Boucher <rboucher@gmail.com> schrieb: >The spec doesn't seem to have any recommendations on this point, but >should an OAuth v2 API always return the same access token if the same >client makes multiple requests? Is there any benefit to not generating >a new access token for each request? I don't see any. >Similarly, if you do generate new >access tokens (as I am doing now), should you also generate new refresh >tokens? Depends on the grant type. I would expect an authz server to generate new refresh tokens for "code", whether the authz server creates a new one for grant type "refresh_token" might depend on server impl. and client-specific policy (refresh token rotation). > >An unrelated question about revoking access tokens when the same >authorization code is used more than once: should refresh tokens also >be revoked? Does it make sense to not revoke refresh token? Otherwise, it could be used to obtain fresh access tokens. > And, if so, should any tokens issued with that refresh >token then also be revoked? It seems :-) sounds reasonable but not nessessarily feasable > simpler (if slightly less correct) >to just revoke all access tokens for that specific client/resource pair >in that case, rather than tracking the ancestry of all tokens. Generally, I would consider revoking access tokens more difficult then revoking refresh tokens. It depends on your token design. One can use handles for refresh tokens and self-contained access tokens and revoke refresh tokens only. In that case, I would limit the access token lifetime in order to force a periodic refresh. Regarding client/resource: Depends on whether you are able to really identify a particular client instance. Otherwise, you would revoke tokens for different (potentially a lot of) client installations using the same client_id. regards, Torsten. > >Thanks, >Ross_______________________________________________ >OAuth mailing list >OAuth@ietf.org >https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Multiple access tokens Ross Boucher
- Re: [OAUTH-WG] Multiple access tokens Torsten Lodderstedt
- Re: [OAUTH-WG] Multiple access tokens Torsten Lodderstedt
- Re: [OAUTH-WG] Multiple access tokens William Mills
- Re: [OAUTH-WG] Multiple access tokens Ross Boucher