IETF Logo Mail Archive

Re: [OAUTH-WG] expires_in

Chuck Mortimore <cmortimore@salesforce.com> Tue, 18 December 2018 15:17 UTC

Return-Path: <cmortimore@salesforce.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 E2035130EC1 for <oauth@ietfa.amsl.com>; Tue, 18 Dec 2018 07:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=salesforce.com
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 ZAjBDcEmC-WO for <oauth@ietfa.amsl.com>; Tue, 18 Dec 2018 07:17:32 -0800 (PST)
Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CAAA12896A for <oauth@ietf.org>; Tue, 18 Dec 2018 07:17:32 -0800 (PST)
Received: by mail-io1-f51.google.com with SMTP id x6so13008335ioa.9 for <oauth@ietf.org>; Tue, 18 Dec 2018 07:17:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=F1Oies4FVGbLYQ1V1qBhlX6zVrdGEoRUiSof/J8gqw8=; b=auZ4HOu+9eIDQU6b64NcTsiGpphRCrCf9nCgbK1bTpVU3Pn1XwLBZghf+AbXyTlrCa ni0VR4T8ZoBviGx7HvcacbKh1KsaXY3AmLQwLm7NlDXz/qYYeuI7v+4zUTfymhWdsHFA ineUjCeG/8e39zH/xGZKwGqITyZ1+0y75d7Ko=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=F1Oies4FVGbLYQ1V1qBhlX6zVrdGEoRUiSof/J8gqw8=; b=bcMvCZbJwvzAjn5HsGUlDLYYSjpO2Tz75IIijWQ97jW+0WfTf1I+qpnOjJcsXWguX0 RIlg+tBZE3do7cMkwxFF9D2MnZwYAsyNdCi0YuraRsa2se4CYXcmT2zt3wZA/JG7SGR2 ArSoQOO5v+H9T/VwtPmFTr+VpuIIgiWs7O49VNPbbb0E5KAoI5Qfd/dIRUXqGhl+1v0i XDcfiCm/pnM19YNhllTElLnYy+EGqskVuXH0tOjcoGy9yBwbiLePNwpv/RzeqjGYaXn2 Onka7Y8jyfcD6ylIHoJgApcfJYYJ/aPj4sCycOGrwnxicDCB4qa/B+fVmsDivwa4SRMz 26zA==
X-Gm-Message-State: AA+aEWY1Yl/5NfZBkZSUArzcTw1vv3xqJi+GdqRJAnPy3DAIHNl1BhE9 nrWlL5/OmJtgtTlpHGjV0cLrfOjKnS/tT8S6yYicFQ==
X-Google-Smtp-Source: AFSGD/W37A83Y7yfHPwdwipshxtSOLW2f3PXWsS+y4RSVghYK8I4mQ+eSMGc4OWRAY4vf5Qu0X78sUby1pYcwKXgZI8=
X-Received: by 2002:a6b:5a14:: with SMTP id o20mr14051082iob.206.1545145578991; Tue, 18 Dec 2018 07:06:18 -0800 (PST)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Tue, 18 Dec 2018 16:06:18 +0100
From: Chuck Mortimore <cmortimore@salesforce.com>
Mime-Version: 1.0 (1.0)
References: <VI1PR0801MB2112D57E9871898418E0BF9EFABD0@VI1PR0801MB2112.eurprd08.prod.outlook.com> <66E27956-1627-46B5-AF60-B7F0CD631513@alkaline-solutions.com> <2ef34983-31b1-9b2a-a28f-ff4e14b2045d@ri.se>
In-Reply-To: <2ef34983-31b1-9b2a-a28f-ff4e14b2045d@ri.se>
Date: Tue, 18 Dec 2018 16:06:18 +0100
Message-ID: <CA+wnMn-CtnBBmgxn9DoLN8CPhiyqkKd1Lj1cauFYNhhe1yYuSg@mail.gmail.com>
To: Ludwig Seitz <ludwig.seitz@ri.se>
Cc: oauth@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/PEzmhUOijczBAnnyS0YLo_yuxBE>
Subject: Re: [OAUTH-WG] expires_in
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Dec 2018 15:17:49 -0000

We don’t issue expires_in for two reasons

1) we have variable length access tokens who’s lifetime can be
extended through activity and we find clients misinterpret expires_in
to be absolute (or have no practical means of finding out when it
updates)

2) we find it actually makes things worse - with proactive knowledge
of when a token expires, aggressive clients tend to keep it alive or
proactively refresh the token.  As a result the intent to limit the
length of the access token actually causes it to be extended in
practice.

> On Dec 18, 2018, at 4:17 AM, Ludwig Seitz <ludwig.seitz@ri.se> wrote:
>
>> On 18/12/2018 12:59, David Waite wrote:
>> My understanding was that this parameter was advisory to the client -
>> it neither mandated the client discard the token after the expires_in
>> time, nor has a requirement that the token is no longer honored by
>> protected resouces at that point in time (vs earlier or later).
>
> That is my understanding as well, I would however have expected that this parameter would be aligned with the 'exp' claim of the token.
>
> /Ludwig
>
>
> --
> Ludwig Seitz, PhD
> Security Lab, RISE
> Phone +46(0)70-349 92 51
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email