[OAUTH-WG] PKCE and refresh tokens
Albin Nilsson <albin@bergson.nu> Fri, 28 February 2020 15:47 UTC
Return-Path: <albin@bergson.nu>
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 2FAE93A1A7C for <oauth@ietfa.amsl.com>; Fri, 28 Feb 2020 07:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NO_DNS_FOR_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 wwAF3OIqKm8g for <oauth@ietfa.amsl.com>; Fri, 28 Feb 2020 07:47:03 -0800 (PST)
Received: from smtpout-36.fbg1.glesys.net (smtpout-36.fbg1.glesys.net [IPv6:2a02:751:100:1::36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5AC13A1A83 for <oauth@ietf.org>; Fri, 28 Feb 2020 07:47:02 -0800 (PST)
Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) by mail-halon-01.fbg1.glesys.net (Halon) with ESMTPSA id 8cf6a0d3-5a41-11ea-bd3c-0bec97ae8c39; Fri, 28 Feb 2020 16:46:59 +0100 (CET)
Received: by mail-lj1-f178.google.com with SMTP id d10so3802104ljl.9 for <oauth@ietf.org>; Fri, 28 Feb 2020 07:46:59 -0800 (PST)
X-Gm-Message-State: ANhLgQ1mhLn2xKQNRkiTJRJ2LcQuzagJYtNzPzp7BuZcgDOP78B8Cxim SoS+6Xd95DwkJ9Os82mtqOjAHs722UTx6CH9bYw=
X-Google-Smtp-Source: ADFU+vtMt7IHmJz4hKU+2RM3AA631E0McfxXfDD68d0dYwRl+hgC0U3YF/hO65K/ntxAApYCXbVaM/boVLHRIyNGdvM=
X-Received: by 2002:a2e:6f19:: with SMTP id k25mr3364461ljc.84.1582904817112; Fri, 28 Feb 2020 07:46:57 -0800 (PST)
MIME-Version: 1.0
From: Albin Nilsson <albin@bergson.nu>
Date: Fri, 28 Feb 2020 16:46:46 +0100
X-Gmail-Original-Message-ID: <CANhzChNLXZBr-HaUX_jZG_kk=5gM6j79gQ0YYmy=HJ=6YFtwzw@mail.gmail.com>
Message-ID: <CANhzChNLXZBr-HaUX_jZG_kk=5gM6j79gQ0YYmy=HJ=6YFtwzw@mail.gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000565ae0059fa4bff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/nQBcyNPj5jXHV3Jfz3FfyyOksmc>
Subject: [OAUTH-WG] PKCE and 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: Fri, 28 Feb 2020 15:48:32 -0000
Hello, I'm having some trouble with oauth and the Authorization Code flow and PKCE. How can I get a refresh token? The refresh token flow requires a client_secret, but PKCE prohibits client_secret. Is refresh token a no go? Kind regards, Albin
- [OAUTH-WG] PKCE and refresh tokens Albin Nilsson
- Re: [OAUTH-WG] PKCE and refresh tokens Ron Alleva
- Re: [OAUTH-WG] PKCE and refresh tokens David Waite
- Re: [OAUTH-WG] PKCE and refresh tokens Naveen Agarwal