Re: [OAUTH-WG] PKCE & Hybrid Flow

Dominick Baier <> Wed, 27 January 2016 07:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 428E81B2C45 for <>; Tue, 26 Jan 2016 23:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iUdRxax2yKr5 for <>; Tue, 26 Jan 2016 23:10:33 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C79A41B2C3C for <>; Tue, 26 Jan 2016 23:10:32 -0800 (PST)
Received: by with SMTP id 17so21238lfz.1 for <>; Tue, 26 Jan 2016 23:10:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:content-type; bh=Yvvrmr4aBP8FchzTqyU8gbXzisTm7m6jmUC9f4vh9wo=; b=swe/Uk6jfG/3IoDSbKwatGhJpJ/rIjasXT6Sjs1XtiZsD49WUcC9SacgsXlnOSQqT4 Z4nh6xsK+15FaFT06HuVn/2H8TtFXiFmpT58KrTv0RZHym80fkDy8/P0wviBIXiu8uDr xOFOS/0yh9l9Re0Fij9IS5IGwcRQf0OAVIh1ml/kvYPVBTpMHaGHs7KJFjry6HNN1qWc jEsML00CRzDk9ypFpXcUvhoe+yfx8Ei0ZajeWm2+j1+IVPZZNAu5UKrYcW0fPqbA18F/ clsfLF1Qu/Ba6vYp/OSh5dnR8ynDLa7iKShCf58O3QIJRsrnOh21l1f6dgMe2xFHLyZh sITw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-type; bh=Yvvrmr4aBP8FchzTqyU8gbXzisTm7m6jmUC9f4vh9wo=; b=hdxUuq69Qf/LvLSPzg0WO4zikXrRmmu3w9XJMevfryDSjFHI5IF/4EWFk0OG2NQTsr kwiqWj3Eg7bd8wYK5sAcDSBGn9bqXbbbf6NcOvDgyCHWHlftPz2n1R3XCPsf6fYlJHvd PtO5fXaIVtTfx+3k2TDle3kFEENeAfCnFCuXVc603okWxyldQLdvhLa4bsM0wPdPvez7 Yhe/YNXSMafAtn06xZG42843qvDVBpJFtUEOC5SEENWYfuvAjcuX7hh5OVnxusjaUWM6 S0ThDtR8TO1f1++15xdNFSK5tRidH5OCZtyEUcSMx8BeSXPms1W0ozbfslDQ+EEsZE19 awTg==
X-Gm-Message-State: AG10YOSKltiEVgIPf7KlTbl7F192EaYOi5sg51NrEtovCAOXTOPNujqr+VIlQVvOT8R8Qw==
X-Received: by with SMTP id 205mr8073047lfe.90.1453878630867; Tue, 26 Jan 2016 23:10:30 -0800 (PST)
Received: from dombp.local ([]) by with ESMTPSA id i192sm630310lfb.14.2016. (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jan 2016 23:10:29 -0800 (PST)
Date: Wed, 27 Jan 2016 08:10:28 +0100
From: Dominick Baier <>
To: Nat Sakimura <>, John Bradley <>
Message-ID: <etPan.56a86d65.9ac2ddf.289@dombp.local>
In-Reply-To: <>
References: <etPan.56a7d2ec.b71f1ef.289@dombp.local> <> <>
X-Mailer: Airmail (351)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="56a86d65_7bb00ece_289"
Archived-At: <>
Subject: Re: [OAUTH-WG] PKCE & Hybrid Flow
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Jan 2016 07:10:35 -0000


we are almost done implementing PKCE in identity server.

And yea - a comment that PKCE applies to whenever a code is involved would be probably helpful for other implementers. Even if that makes total sense, it is not obvious.

Dominick Baier

On 27 January 2016 at 03:11:28, Nat Sakimura ( wrote:

To the end, perhaps amending RFC6749 so that the response type is treated as a space separated value would be a better way to go? 

2016年1月27日(水) 5:20 John Bradley <>:
Yes it also applies to the “code id_token” response_type.   It would also apply to “code token” , “code token id_token” response types as well though I can’t think of why a native app would use those.

We can look at a errata to clarify.  It is a artifact of resonse_type being treated as a single string as opposed to being space separated values as most people would expect.

John B.

On Jan 26, 2016, at 5:11 PM, Dominick Baier <> wrote:


PKCE only mentions OAuth 2.0 code flow - but wouldn’t that also apply to OIDC hybrid flow e.g. code id_token?

Dominick Baier

OAuth mailing list

OAuth mailing list