IETF Logo Mail Archive

Re: [OAUTH-WG] Refresh tokens

Leo Tohill <leotohill@gmail.com> Mon, 22 July 2019 02:22 UTC

Return-Path: <leotohill@gmail.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 49B111201B7 for <oauth@ietfa.amsl.com>; Sun, 21 Jul 2019 19:22:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RuN8scfb3eK9 for <oauth@ietfa.amsl.com>; Sun, 21 Jul 2019 19:22:42 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 5A41612013F for <oauth@ietf.org>; Sun, 21 Jul 2019 19:22:42 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id f5so8074751pgu.5 for <oauth@ietf.org>; Sun, 21 Jul 2019 19:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iGetok8ctiKf12/L+m9L/4O8NIon1qMpr4wdhZYtoW8=; b=qaEjwM5KdPs/dv0A2qKzI6/hqkl8ZsiWVl0AdoWc9pc33SNs9/EEzeJWz5/JXD05Ay AIxPMCA4ZFJTaHPZt6YkNG6uivh/UOyghAP7n6RCBpFpP1FcBLuE8YUdUYayBJrE2STw aOuL7+4H/OYT0D74yEnSjd5lcVKPpc8BJiaYALN4Cn1TbJAIx2nHnqp5tw3jg0salplE 6c/vqdlAg8s1TM5sKnzNjkM2mLL7TpuhN6BZEauVeSwIU+Xqt7OowXoF8FMbSOOpNEnL hVBsjYFQaWVvs2pfZgjGs3CpaKpbyRfoipBZ0axm/87hc909W4OBsF7yYbJGDhZ/tk7O UCfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iGetok8ctiKf12/L+m9L/4O8NIon1qMpr4wdhZYtoW8=; b=XDtWoJS097KG39cG2PSnsyzvAesE26YwNi87IFLsKtYALB1vd82S3YjbeGySZc9lJi WJnS+DJyqKbcp+IiLhk78LmxwuiDFk8UjSeYMXBc873oYOdzsGnnLNnPBRZvJl4qlsJ2 ugmbLOCf7wjyfs5iYMJXoZh4h/AxUVoKZm8Vj+Yez0fQ3oe4Kb1jRQpd17Q1W5+Kfdts JJlP5ckZ+MQK12pqki87suTKCX661NutA7dTFEjVS31nIzYmeeNpBh8h3jnBKWYC9Q6e XXwdrEIqDVyp4bZkyiRzlLsKgwt7rUJtBzqDiCKy4amX/LqY6qzwHAgaCDgbRATI4ebD tDMQ==
X-Gm-Message-State: APjAAAVkPGSLgBF6fcut2T4qgc/xBSCUxvQzgjmO9IFh4DJtRRaa+s3x QTLHCDb0n4y0REY3Py1VnAohg5KXUgnXzzVHp1w=
X-Google-Smtp-Source: APXvYqx96uIaG8uSdafB+mpUReoEfex1Iq5Q170Jd2r9YVyoIUHMGLDYrRCoMa0tUFEEqhX8+haZe7RZDeXZmsATCV4=
X-Received: by 2002:a63:1d4:: with SMTP id 203mr51718955pgb.441.1563762161774; Sun, 21 Jul 2019 19:22:41 -0700 (PDT)
MIME-Version: 1.0
References: <CABw+FcsH3CHmFphz5DD6aDeEqKLxbQhY14kdrXCVY0WXQN6PuQ@mail.gmail.com> <AEC7268A-D22D-41DA-8609-E7D2DD3B290C@alkaline-solutions.com> <624da319-b19c-053b-4fd0-048c0e2b8fb9@aol.com> <CAGBSGjp8m+V+i-sNnrLmu7DR_Bo1uv0iGkW2o7hiqUWw8Sc7qg@mail.gmail.com> <138cbde0-11b7-8f23-1028-3af0846b5a01@aol.com> <CAGBSGjq=SFG5nfOA6nwRsEQY576dsJDAHaL9UH4Yh7AAtOMu5Q@mail.gmail.com> <D676DDDE-20FE-4004-8E3F-124A560A1C20@mit.edu> <0A6F7761-9376-43EE-9B9C-0554812E13B7@forgerock.com> <CABw+Fcus9e5Et5aU_70tJwoX5BVfWaFbiJ+f4UgKe2zr46UPvQ@mail.gmail.com> <20C9E1B6-E497-41C9-9590-F68DD747E401@alkaline-solutions.com> <CABw+FcspWmjRGRuNcudCivuj=GmbWR0sA_s5oNZJFc8Jc6nToQ@mail.gmail.com> <170d4112-fc89-4f6b-8f10-126baf62a193@getmailbird.com>
In-Reply-To: <170d4112-fc89-4f6b-8f10-126baf62a193@getmailbird.com>
From: Leo Tohill <leotohill@gmail.com>
Date: Sun, 21 Jul 2019 22:22:32 -0400
Message-ID: <CABw+FctQrGWuqs3sSjTdGTBtDdRRTuAGq6dC42XDJi6mBGb89g@mail.gmail.com>
To: Brock Allen <brockallen@gmail.com>
Cc: David Waite <david@alkaline-solutions.com>, OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002a73ed058e3bc083"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Yvi3rxJUKJ6RTUw0YE_r6Bd6eRg>
Subject: Re: [OAUTH-WG] Refresh tokens
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: Mon, 22 Jul 2019 02:22:50 -0000

I left out Okta
<https://developer.okta.com/docs/guides/refresh-tokens/overview/>(how could
I?)  - it supports a refresh token expiration, but I couldn't find doc on
the details.


On Sun, Jul 21, 2019 at 10:44 AM Brock Allen <brockallen@gmail.com> wrote:

> > IdentityServer allows a choice of behavior on refresh token expiration
> time. It can have a absolute expiration time, or use a sliding window.
>
> FWIW, in addition, those can be used together -- sliding & absolute.
> Finally, refresh tokens can be re-use or one-time use only. These are all
> per-client settings.
>
> -Brock
>
>

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