IETF Logo Mail Archive

Re: [Ace] Overwriting Tokens

Stefanie Gerdes <gerdes@tzi.de> Wed, 12 December 2018 10:17 UTC

Return-Path: <gerdes@tzi.de>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F0C130DC6 for <ace@ietfa.amsl.com>; Wed, 12 Dec 2018 02:17:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WgjCustOMpn for <ace@ietfa.amsl.com>; Wed, 12 Dec 2018 02:16:59 -0800 (PST)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16D4A130DBE for <ace@ietf.org>; Wed, 12 Dec 2018 02:16:59 -0800 (PST)
Received: from [192.168.1.109] (p508A4EFC.dip0.t-ipconnect.de [80.138.78.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 6F7822052D for <ace@ietf.org>; Wed, 12 Dec 2018 11:16:57 +0100 (CET)
To: ace@ietf.org
References: <154322421294.8323.8505315870685563404.idtracker@ietfa.amsl.com> <cbd083d1-cb95-0732-aa8b-7c7de3f480d1@ri.se> <a0cdd836-7fe3-339e-0c48-961503857447@tzi.de> <043bc23f-f566-55d0-7c94-200d72b98341@tzi.de> <b22fece0-cabb-b387-74a0-1a786056eb08@ri.se>
From: Stefanie Gerdes <gerdes@tzi.de>
Message-ID: <c9f0deca-5cf8-e36d-b150-feabb0c8b82e@tzi.de>
Date: Wed, 12 Dec 2018 11:16:57 +0100
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <b22fece0-cabb-b387-74a0-1a786056eb08@ri.se>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/UnBy_nRDSDiHfKLwDQ2piv-ri80>
Subject: Re: [Ace] Overwriting Tokens
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2018 10:17:01 -0000

Hi Ludwig,

On 12/12/2018 11:05 AM, Ludwig Seitz wrote:
> On 12/12/2018 10:33, Stefanie Gerdes wrote:
>> Hi again,
>>
>> I have one additional comment to ace-oauth-17:
>>
>> Section 5.8.1 recommends that RS stores only one token per key and that
>> existing tokens are overwritten by new tokens. I wonder how the RS knows
>> which token is the most recent. I don't think the expiration time helps
>> in this case because it should be possible for the AS to
>> provide a token that expires earlier than the previous token.
>>
>>
>> Viele Grüße
>> Steffi
>>
> 
> "Recent" here is meant as "most recently received". That is something
> the RS definitely can track.

The token most recently received by RS is not necessarily the newest.
A client may (accidentally or not) send the older token later than the
newer token.

Viele Grüße
Steffi

v2.23.0 | Report a Bug | By Email