[OAUTH-WG] draft-bertocci-oauth-access-token-jwt-00

Vittorio Bertocci <vittorio.bertocci@auth0.com> Sun, 24 March 2019 23:29 UTC

Return-Path: <vittorio.bertocci@auth0.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 1FD931201EA for <oauth@ietfa.amsl.com>; Sun, 24 Mar 2019 16:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=auth0.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 EB8eBphtO6qJ for <oauth@ietfa.amsl.com>; Sun, 24 Mar 2019 16:29:18 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 361291201E3 for <oauth@ietf.org>; Sun, 24 Mar 2019 16:29:18 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id a6so4693671lfl.5 for <oauth@ietf.org>; Sun, 24 Mar 2019 16:29:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=auth0.com; s=google; h=mime-version:reply-to:from:date:message-id:subject:to; bh=h/Yqvah02vIA1xYz/oYNE+9ucqpYMApcFPCFo366imU=; b=BT+P5QgbIc40oXqAYgwCxKepeNcrdueGdWExICx0LGLcWNmnDueuFMVua2rjZDHAlk 7Qls8wn/9q0nN7Jr7QqZ7Po7Kx9HSsW2XvKnL3zLnW9Oi64CT62iXv2iYPXAJOni5mqF y+pPcBIpxkic7KpyYfy5CDDaUU63QzLT75YVtW7w7df5wfyIyCunDab9nEP5ZU2XKYs2 YCIuC9Ex3dmMLwDtiYq+H29wdZw5qy1XVqEWGzibmabPQDbrcJkxUQtEUNEQZDqNAzbU CguAVHX4ccpIBsLkvJvFZIJ9+7KTrb2RGAmWVvjn58iT15itstCG8w2iIPChX0miKPH8 OgwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to; bh=h/Yqvah02vIA1xYz/oYNE+9ucqpYMApcFPCFo366imU=; b=haqFJkDVF0lF68kXYqGezdC/mntDAUwGHq7RZshA+yrTmRU4rDLgC8GVtLQsV2Ghdp INyFQzteAW44RtYSRNRQKWhRaJfnNYeK4/EVxC7kqa97UlKeYsHl4fzwwB4VNWtz6QEu 9xhkxqx1gFbCz/zV5TySCLsGdJussnRJcjho2Pg6PUlSCE1n7PjWRZiV2/lykcWLk/JN CK2+C0Ms2lcL8ZTimJ/svySrxO7e6M7M0hQobGMXZvrDp1rvzUSHfA8taCw/WV30Yhbh oSIegoTDL8RCcayjlndh05EzBVBLsjD+I66HT1Y1pomco4XUUP34r/NMzMBiUlFb8E/Z GZgg==
X-Gm-Message-State: APjAAAVqkf87j7YDIby6MVmx24mDV/uY+0VsWnlQpSTfnUBXqhCT1u/o F3tanwpek4ztW/LfNUhBJcJkQjE2oMZF/2hDVpCBMtjZ1f3V6w==
X-Google-Smtp-Source: APXvYqyfaJo8O+wOs+NFhRoqnC/TyCxE451wfrSX0CPjR7mneUfMvFsejUhnV0Vdp9vK7/wLoS/78NMnRfqZ4CJ8s70=
X-Received: by 2002:a19:9e0d:: with SMTP id h13mr10389150lfe.51.1553470155877; Sun, 24 Mar 2019 16:29:15 -0700 (PDT)
MIME-Version: 1.0
Reply-To: Vittorio@auth0.com
From: Vittorio Bertocci <vittorio.bertocci@auth0.com>
Date: Sun, 24 Mar 2019 16:29:05 -0700
Message-ID: <CAO_FVe6eWy3zppQAij7qxD+ycYL8ebqGJKG0y-A7GhN+0=kb4g@mail.gmail.com>
To: IETF oauth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cf7fb10584df74d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Iw6w1VX21RjYfRKkwZd1N-fp7vk>
Subject: [OAUTH-WG] draft-bertocci-oauth-access-token-jwt-00
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: Sun, 24 Mar 2019 23:29:21 -0000

Dear all,
I just submitted a draft describing a JWT profile for OAuth 2.0 access
tokens. You can find it in
https://datatracker.ietf.org/doc/draft-bertocci-oauth-access-token-jwt/.
I have a slot to discuss this tomorrow at IETF 104 (I'll be presenting
remotely). I look forward for your comments!

Here's just a bit of backstory, in case you are interested in how this doc
came to be. The trajectory it followed is somewhat unusual.

   - Despite OAuth2 not requiring any specific format for ATs, through the
   years I have come across multiple proprietary solution using JWT for their
   access token. The intent and scenarios addressed by those solutions are
   mostly the same across vendors, but the syntax and interpretations in the
   implementations are different enough to prevent developers from reusing
   code and skills when moving from product to product.
   - I asked several individuals from key products and services to share
   with me concrete examples of their JWT access tokens (THANK YOU Dominick
   Baier (IdentityServer), Brian Campbell (PingIdentity), Daniel Dobalian
   (Microsoft), Karl Guinness (Okta) for the tokens and explanations!).
   I studied and compared all those instances, identifying commonalities
   and differences.
   - I put together a presentation summarizing my findings and suggesting a
   rough interoperable profile (slides:
   https://sec.uni-stuttgart.de/_media/events/osw2019/slides/bertocci_-_a_jwt_profile_for_ats.pptx
   ) - got early feedback from Filip Skokan on it. Thx Filip!
   - The presentation was followed up by 1.5 hours of unconference
   discussion, which was incredibly valuable to get tight-loop feedback and
   incorporate new ideas. John Bradley, Brian Campbell Vladimir Dzhuvinov,
   Torsten Lodderstedt, Nat Sakimura, Hannes Tschofenig were all there and
   contributed generously to the discussion. Thank you!!!
   Note: if you were at OSW2019, participated in the discussion and didn't
   get credited in the draft, my apologies: please send me a note and I'll
   make things right at the next update.
   - On my flight back I did my best to incorporate all the ideas and
   feedback in a draft, which will be discussed at IETF104 tomorrow. Rifaat,
   Hannes and above all Brian were all super helpful in negotiating the
   mysterious syntax of the RFC format and submission process.

I was blown away by the availability, involvement and willingness to invest
time to get things right that everyone demonstrated in the process. This is
an amazing community.
V.