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

Torsten Lodderstedt <> Tue, 07 January 2020 09:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BCB0112008D for <>; Tue, 7 Jan 2020 01:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CfumjZpX7xKl for <>; Tue, 7 Jan 2020 01:19:23 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F2B3612081F for <>; Tue, 7 Jan 2020 01:19:22 -0800 (PST)
Received: by with SMTP id z7so52959679wrl.13 for <>; Tue, 07 Jan 2020 01:19:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=SLPVLz3zSiP9N67zHlNnAokTUQ6tIFFY75PnE+OpArk=; b=r8YIw10Dn6az4F8OfYop8yWD8A+V4LqXDtQdGUfB/nWEZNkjgY06BbXAE31sKfJwLU TBWM4Bj1I/5sGUPqqbkvupiRAHWQesvoqtLkNw23cwUqXjlyZ76wC4gL0CV+2tvw/d3W r/dvY/HQYfjaIoCqnzK2OJsGWXxazf5t8ZT/W5W3r9Tv2GavO/QT2iEFKWs8kpk/Ljsl +98LpSAe8ZYEG7kEVkrfZnKN+OWr3ubdlB08xfYI2Cwa+8sGNtJntj9JWSeAFge7RIBY heMO5MyMnNbihsd9wVfh7SHMpr4vkQrLZGzQ11oPw18im55LAXQvPMs96Oc1ztroS6NT +eWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=SLPVLz3zSiP9N67zHlNnAokTUQ6tIFFY75PnE+OpArk=; b=bcpv8+NMe/UHiYCk9HfvCALPtk/fQU49jvwM+O0JlWKHwOhzZzPVx8pTzPcn90+0au yKblFU8F6jN95U1jNHqaG/TciFmOQ++pMWM2azHyFZaVDR5tFQjaOCj7A0q3IIcGCTWG 6ksG43GkxzDnOeFB5mv55JWwpb7mtMu6Plzy+KV5v8QbMVrP+ZUoTTtt+FUlr2eiG0Pj 7u92t34Y89Kg7ohyM1TcwzWOiil0ZMD2+1FDXHKcRdCMoPoEFCIjnGNa1ocg3D/zw1o2 Lxbg+vkl4uvfByS7f9Y0Rpc8IR44kXPh5XG28sOsYyTwvvI+Q3/rTGW0spfk6ptJxUCs hW0A==
X-Gm-Message-State: APjAAAVhrOA/1Mr4YTV01NCdd6W97zRRS5bt4YC3WoJXGm1vEZ6wGAds A6c9+s0JzL/lbXbtBoDlnqDMVva/X/udG4WX
X-Google-Smtp-Source: APXvYqz5se6EOe3P8AyhnnKvbKYrNDdKQ1Vw+H5iosQ5ueLkrLgYmriOW3A/rbq+WwX7TglAzE3SFg==
X-Received: by 2002:a5d:6551:: with SMTP id z17mr113884975wrv.269.1578388760994; Tue, 07 Jan 2020 01:19:20 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id m7sm25783612wma.39.2020. (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Jan 2020 01:19:20 -0800 (PST)
Content-Type: multipart/signed; boundary=Apple-Mail-EA73AA6C-7051-429B-B30E-5C2CF6CE62EA; protocol="application/pkcs7-signature"; micalg=sha-256
Content-Transfer-Encoding: 7bit
From: Torsten Lodderstedt <>
Mime-Version: 1.0 (1.0)
Date: Tue, 7 Jan 2020 10:19:19 +0100
Message-Id: <>
References: <>
In-Reply-To: <>
To: John Bradley <>
X-Mailer: iPhone Mail (17C54)
Archived-At: <>
Subject: Re: [OAUTH-WG] JWT Secured Authorization Request (JAR) vs OIDC request object
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Jan 2020 09:19:27 -0000

> Am 06.01.2020 um 23:50 schrieb John Bradley <>om>:
> A client could duplicate those outside the request object for some sort of backwards compatability but they will be ignored.
Is this used for backward compatibility with the OIDC servers?
> What we have lost is the merge capability.  There are some use cases that could use that to have a presigned object that some paramaters like state are outside.  

Is this option used in the wild? As far as I understand the main use case is a 3rd party signing the request object that way entitling the client for something. I‘m asking since in my experience any kind of entitlement by a 3rd party is handled behind the scene using registries.