IETF Logo Mail Archive

[OAUTH-WG] [JWT Profile for OAuth 2.0 Access Tokens] Adding state into the JWT

Prabath Siriwardena <prabath@wso2.com> Thu, 07 May 2020 18:56 UTC

Return-Path: <prabath@wso2.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 761FF3A08B3 for <oauth@ietfa.amsl.com>; Thu, 7 May 2020 11:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=wso2.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 TYLz5fG3i9Ue for <oauth@ietfa.amsl.com>; Thu, 7 May 2020 11:56:46 -0700 (PDT)
Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (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 21F253A0894 for <oauth@ietf.org>; Thu, 7 May 2020 11:56:45 -0700 (PDT)
Received: by mail-vk1-xa2d.google.com with SMTP id v23so1761895vke.13 for <oauth@ietf.org>; Thu, 07 May 2020 11:56:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=w57QxFSZ9+zL13TkMMMleTNmf935OJWiQFcvkWxcgTU=; b=UBC4L5U4fWzLHsbeOovh6KUca14JfAXpKdCvZ2kr3oYzmctpHH3cKM7cKROwNvdAbx cqGKxw9PCrwt2kCKfhdMwh9bWhZmPVNsvITKPobohTmPpYi/jAE0vEv5/syLiHyd8rWE KV/CAt2xEkEQvvzdGLheXtiBm6sFTc1BJnsbE=
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; bh=w57QxFSZ9+zL13TkMMMleTNmf935OJWiQFcvkWxcgTU=; b=KUHlXbqcEB2MOjNdo57oeASw+g5vFPXg46OcS6aP8y6I718Kbvt5GQU7sVGUU/HgjQ Kzc84Njb8TRqtRk0yuUb+RidYGcL2Eq42e2xmAArU5od45lD1werO15fPjhlZJ5nt05L 9Q3/IQRfixnMYfr7UEIom4FpXtS+VlHEu1NDjbJcJWhu77uOAdehKjdaL7iiFHkZrvw8 7EHwFz/sHlEtthbUgJNN9l9+g+GUiLx9dqaOxSWuFJwVcJbXdd1iEcOve9ublTrHtwm6 TvIWy05bKjVTlNcyHz9v8gl9aPKbRI+gpgbQ0f5Dpdh+4YOZqhupmeIoyrqUMXwxDTxt FMJg==
X-Gm-Message-State: AGi0PuaSxZaAyDH1D5i/7ceDa7UOaDZFl/flUd8+/DLs5nm1EZJrmsCi FRFGHnKL37bF59jQi8t4ywUDxBTmtfyX2gHntw0SZw==
X-Google-Smtp-Source: APiQypI+ozJXihlBMIy2XP1x6/XuwTh23MqL8O1Q9EQ7m3NqC/p9eFRzR9jxsajnz+lY6zPcGjWkoaXvF+tEnHarYbc=
X-Received: by 2002:ac5:c76d:: with SMTP id c13mr13143948vkn.3.1588877804342; Thu, 07 May 2020 11:56:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAGL6epKZhnketE3=XbSBvyBSk8NH_c1c0Pay6+QjL7HKa=fsJQ@mail.gmail.com>
In-Reply-To: <CAGL6epKZhnketE3=XbSBvyBSk8NH_c1c0Pay6+QjL7HKa=fsJQ@mail.gmail.com>
From: Prabath Siriwardena <prabath@wso2.com>
Date: Thu, 07 May 2020 11:56:34 -0700
Message-ID: <CAJV9qO8Ve9mwpF5FU4OYzfqBTkZ=b5dUOo=RwWBbchTM-WRY4Q@mail.gmail.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001eaa2105a51371e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/OqZljlsAXVayFyXp50fy38IWlos>
Subject: [OAUTH-WG] [JWT Profile for OAuth 2.0 Access Tokens] Adding state into the JWT
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: Thu, 07 May 2020 18:56:49 -0000

Hi all,

Can we say in [1], that the AS should add the value of *state* parameter
from the authorization request (if present), to the JWT access token it
generates?

This will help to address token injection issue [2], with respect to the
implicit grant type.

Appreciate your thoughts on this.

[1]: https://tools.ietf.org/html/draft-ietf-oauth-access-token-jwt-07
[2]:
https://tools.ietf.org/html/draft-ietf-oauth-security-topics-15#section-4.6

Thanks
-Prabath

On Tue, May 5, 2020 at 11:19 AM Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
wrote:

> Hi all,
>
>
>
> This is a 3rd working group last call for "JSON Web Token (JWT) Profile
> for OAuth 2.0 Access Tokens".
>
>
>
> Here is the document:
>
> https://tools.ietf.org/html/draft-ietf-oauth-access-token-jwt-07
>
>
>
> Please send your comments to the OAuth mailing list by May 12, 2020.
>
>
>
> Regards,
>
>  Rifaat & Hannes
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email