IETF Logo Mail Archive

[OAUTH-WG] Re: Refresh Token Rotation

Warren Parad <wparad@rhosys.ch> Fri, 02 August 2024 11:08 UTC

Return-Path: <wparad@rhosys.ch>
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 DACA6C14F682 for <oauth@ietfa.amsl.com>; Fri, 2 Aug 2024 04:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rhosys.ch
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYAGPD4MJHbL for <oauth@ietfa.amsl.com>; Fri, 2 Aug 2024 04:08:46 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D582C14F60D for <oauth@ietf.org>; Fri, 2 Aug 2024 04:08:45 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-530ad984f2dso385491e87.1 for <oauth@ietf.org>; Fri, 02 Aug 2024 04:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rhosys.ch; s=google2024; t=1722596924; x=1723201724; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=jrpvowl3w+Xl1d5jrs03yMA1/bb+Dpxym0DXAFbJaKY=; b=HlsG7lYKqdZlIC8bvbVBReFKhvFL6FY5XCfQr3Yw+9TbKsBRtXe10+euj/h8JM43jI WtLCHJORnDz0Kj3Y8rsYUPSbdfhyYUubArvE7X+sKmRphxYR4J1Uvp8f6B7tK9mrZxBZ UFPXSjHiPzQJyLmxK/l47wKAM51c/DFY7FC8rl+xSIwyHhCOK1OPo7Jr3ltmEwPTLAmZ tl7vAc8k58RtdSmPgA1wMOEHtLxDWuQlbNu3IM9WNH1d1VKOyJ7GOJcovCbp/O54e6PT ZfDCJUJzObs/H215POH7ZYb8bBRwd7HNuch7Y9wQ0LcE46ZH0LPKX9ZMyU9KwEPqVE2C oZsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722596924; x=1723201724; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=jrpvowl3w+Xl1d5jrs03yMA1/bb+Dpxym0DXAFbJaKY=; b=MxHAWdfMzY0MHudpZecVXd1yuzWksMHdEiQ+Mwqv3EO6Wse7hPWnIWZ1TAuDw0btpK imfZbfEcniVIpmssRAZfMrV1bklq0SY1bMoXxcteWcFUJcQT5ERhwxM2HPUOLnmJWgow 4PVHWJMsYMOuNVv305FzNnMKfP9DDYBQ9oxLI5HOWtrp5ML+2/qjENzDX+ttcrb84tRW /pwoPxjn6mGNOSwY7nEWFQAVvWwkQriBYkdcLisQdjFNzasDRkWGmmxC4fSpIjzrMG56 t0UmaoToAZJYqRuV2EWTtfAy024BSTqsIc/df50Bg+zwZSXc4heXE1hn4JKsRhc78FWo UBRg==
X-Gm-Message-State: AOJu0YxmGVt6hgoglIHcDInVFNy4goi1dwBptvJVEHR05b4PPpT88zNA m7ADUoLe5cqm+hmqVD6PFBqvMs7jisid0sKl013BGCZ+FheX3C1KLksIxQbgAqZmgyWqeAe/e5u wemnkiPPCuThQi60VZ5UCzYslvbETSZODz+PW
X-Google-Smtp-Source: AGHT+IHDvyC19oD2oT1Ut92C+8BL+KuynWudUymrFkiQomgA/yvFCvdYFdMSahOcmogyAf3by4e/xoukqpKOwTOnGa4=
X-Received: by 2002:a05:6512:3f29:b0:52e:ff77:5a58 with SMTP id 2adb3069b0e04-530bb3a69fcmr1191962e87.4.1722596924051; Fri, 02 Aug 2024 04:08:44 -0700 (PDT)
MIME-Version: 1.0
References: <CADU05gP9Zn_18bsmmiUgLNVsDGN9HEurJvF30jCbT5-nx4ycMg@mail.gmail.com>
In-Reply-To: <CADU05gP9Zn_18bsmmiUgLNVsDGN9HEurJvF30jCbT5-nx4ycMg@mail.gmail.com>
From: Warren Parad <wparad@rhosys.ch>
Date: Fri, 02 Aug 2024 13:08:32 +0200
Message-ID: <CAJot-L2qJBRfgc2CpnokjP2Dk8iwJ9L7UDBuj+j6a+D6JG99oQ@mail.gmail.com>
To: Indeewari Wijesiri <indeewarii@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bffc31061eb15931"
Message-ID-Hash: ZYVD3ZQKDXSHBBOPNNUVAO5CDSB6OTYB
X-Message-ID-Hash: ZYVD3ZQKDXSHBBOPNNUVAO5CDSB6OTYB
X-MailFrom: wparad@rhosys.ch
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: oauth@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [OAUTH-WG] Re: Refresh Token Rotation
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Gla86eV79UemYfiJTKBf-CAUPl8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>

Indeewari,

I'm confused regarding what you are describing. Would you be able to give
additional context?

- Warren

On Fri, Aug 2, 2024 at 11:25 AM Indeewari Wijesiri <indeewarii@gmail.com>
wrote:

> Hi all,
>
> Refresh token rotation, which involves issuing a new refresh token each
> time an access token is renewed, is the default for the refresh grant. Do
> we follow the same practice for the authorization code grant and password
> grant as well? What is the recommended practice between long-lived refresh
> tokens and refresh token rotation for these grants?
>
> Additionally, is there a specific requirement for refresh token rotation
> with JWT access tokens in the authorization code grant and password grant,
> given that JWT access tokens are renewed per request?
>
> Thanks and Regards
> --
>
> Indeewari Wijesiri
> _______________________________________________
> OAuth mailing list -- oauth@ietf.org
> To unsubscribe send an email to oauth-leave@ietf.org
>

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