Re: [OAUTH-WG] JWT Secured Authorization Request (JAR) vs OIDC request object

Torsten Lodderstedt <torsten@lodderstedt.net> Fri, 10 January 2020 18:13 UTC

Return-Path: <torsten@lodderstedt.net>
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 78155120B27 for <oauth@ietfa.amsl.com>; Fri, 10 Jan 2020 10:13:53 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=lodderstedt.net
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 T5NZi12efbry for <oauth@ietfa.amsl.com>; Fri, 10 Jan 2020 10:13:52 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 C526C120B01 for <oauth@ietf.org>; Fri, 10 Jan 2020 10:13:51 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id q9so2985978wmj.5 for <oauth@ietf.org>; Fri, 10 Jan 2020 10:13:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lodderstedt.net; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=pdLhrn5gTGC3T9Kx5LpI9MnBjLShakyrkG22taxmDdU=; b=AWi4D8rILTvyruzJ72b58H2CGybI0azc/DrpqykPojMvNLrxPS4oXIWOAYCHsFFt2e X/kNll3IxzFDyHwUwyqdVMooBd9ngoZ/PamcrI0vJa5UqQvg0YH4bZcE11FZyCTBtaTw CPmNibabSBy7h8nTh/vcUT66nY7CbJDopmYQkYZKMr+j5U6TYhySCmi5ZwSm6Uo5BsoO 4f1yFaAY77Qk9T11/RKMZbA2wGRfrEl79VwAQB2ssJVib9KsvQpL51wFHl9/zc4c6dUh 09xl5E8N3hYHAM2Eeo0/Te1ArNVepCAtNCh13R9VJbRS+JeC4GvuRHJKBSmFrxPKGMi0 0M5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=pdLhrn5gTGC3T9Kx5LpI9MnBjLShakyrkG22taxmDdU=; b=J/s6jURyYYdr6M/P4SZvogtm6QG3ymtzZERBq0qwCNr9F/m04uIIh85kyFBZMEnuNa eDSfZ+XfNi961g1QUzgJi+WNzC/qka0SFYZU58o1qP+LTph6ItIX+9OSkzW4IVmPlNAt Tjh6XaDnqBmpfA2NGqw7Xyg+KuCYfZxNw1VvoW/01mV/rfAtrhP1jLxcNpN1SSuZ1iF0 0i0SVdiIGjNSROcnAFCKoe1iWef055yap2564c/haceUeL+VGKjY/6daF6shSHkmHaAo BzGNP0WEkcq3CRk+R8IZxnrQ9dmhDoyO8sE20VfAtLnUvBfjdAP6rbC/RFUdF31lDWgs Miwg==
X-Gm-Message-State: APjAAAXc6p8oDKmoGeBe05fJYcxbX28qzU3j4BJnRcPT5QNlx/zQgaCV g95MBOPVkhjyWbpQf7+bTaSaUMkDOHLpao+f
X-Google-Smtp-Source: APXvYqwHf9L7Hvu9DyU/VHiUf9Xr9iTQW0eCErD3pZlFHWpz/Nky8WAqM8NGAxuJkkbyZCfGHRHl3A==
X-Received: by 2002:a05:600c:2488:: with SMTP id 8mr5598756wms.152.1578680030379; Fri, 10 Jan 2020 10:13:50 -0800 (PST)
Received: from [10.30.1.34] ([213.151.95.78]) by smtp.gmail.com with ESMTPSA id t81sm3034371wmg.6.2020.01.10.10.13.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 10 Jan 2020 10:13:49 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Torsten Lodderstedt <torsten@lodderstedt.net>
Mime-Version: 1.0 (1.0)
Date: Fri, 10 Jan 2020 19:13:48 +0100
Message-Id: <8DFAF146-442E-4115-B31C-4BA1AAAABD2C@lodderstedt.net>
References: <CAANoGh+T1=krOtqLXfa45_wjwobfnUpDX0z5eXVYgV9xPqKD5w@mail.gmail.com>
Cc: Justin Richer <jricher@mit.edu>, IETF oauth WG <oauth@ietf.org>
In-Reply-To: <CAANoGh+T1=krOtqLXfa45_wjwobfnUpDX0z5eXVYgV9xPqKD5w@mail.gmail.com>
To: John Bradley <ve7jtb@ve7jtb.com>
X-Mailer: iPad Mail (17C54)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/0J0yFn7ZhKTbwG3rYBfmRBjRzHI>
Subject: Re: [OAUTH-WG] JWT Secured Authorization Request (JAR) vs OIDC request object
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, 10 Jan 2020 18:13:53 -0000


> Am 10.01.2020 um 16:53 schrieb John Bradley <ve7jtb@ve7jtb.com>om>:
> 
> I think Torsten is speculating that is not a feature people use.   

I’m still trying to understand the use case for merging signed and unsigned parameters. Nat once explained a use case, where a client uses parameters signed by a 3rd party (some „certification authority“) in combination with transaction-specific parameters. Is this being done in the wild? 

PS: PAR would work with both modes.