[OAUTH-WG] oauth par - authorize request with client_id
Sascha Preibisch <saschapreibisch@gmail.com> Thu, 05 November 2020 02:33 UTC
Return-Path: <saschapreibisch@gmail.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 1EA693A15FD for <oauth@ietfa.amsl.com>; Wed, 4 Nov 2020 18:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 (2048-bit key) header.d=gmail.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 5ArY8fVAfoDE for <oauth@ietfa.amsl.com>; Wed, 4 Nov 2020 18:33:36 -0800 (PST)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 7F7053A15FA for <oauth@ietf.org>; Wed, 4 Nov 2020 18:33:36 -0800 (PST)
Received: by mail-lj1-x22b.google.com with SMTP id t13so586282ljk.12 for <oauth@ietf.org>; Wed, 04 Nov 2020 18:33:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gOlhj0fE3otscKRuRfx1VYEJfVtTDdBaNriOgNy3yTk=; b=k0iTky8venGD6jN8jjy+jDlPCT6m/xWKlijr2VQz6OzW5qJpZfETGdtTv6274sI2yx JiIjtAzSfa3ePufSW9ud83XWfQaufjw0D3lyQeOrpaU4IiIGgWsm8ci4qzTogs2rSvwq NACXmFE4s1RdBMDN11Kx5ak/4rGT8GvtEFBaSoisZfYEowZ1/T9AuRm0WVOM6y7tnyeH sa8TxlbelANvQYp70xjF2+yToyPnllddqKAp7kcbMljJYtncT0167tcx0pIPX6B1J0m8 4B+Gha66cumfqsCgvs1x72tvSYtHtDezDHxUuW6kPHAYfGfoWfCHxQ+KJnbtI8c+BX+t 4Czg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=gOlhj0fE3otscKRuRfx1VYEJfVtTDdBaNriOgNy3yTk=; b=jUsi45x2d9CZAPkSED08kWv1olL22MdmAMH7WguhHO+npPkydDR8CxtrSFFjoE4P3Q eb+kw1gIPRSvfUx1AVPy+ufSHAkXSJ9RSPxli/TMbX7/3ANg7EaIWliokMDk+AwYGV1Y WTOsAdxK9RZhvpwx6YcdW5cDHE3IBqJWSXPfWCTK4g+Xka7x7XTN3Y1rXAq1f2v3hAcc as1spIU0l41eBot8BSRJA4KfXrOM61loKDskusn7PrUlDtelhSU6sYQZznyn0TeoFYiz hffMS6vnl9758b/zQFhP9sluPmjvvdx1T0b7stRGomfjLku6cryPhsWnbaiz8uNBXI27 jvYQ==
X-Gm-Message-State: AOAM53354vbTixfHqO7q0x3AkPqJz7bpQ5IGWJS4AV8O3iUatfXF0iNZ 22biStiiZCRVt5JU+vqsDdExc1JtJHH2QIEqwezcI53jydcUNw==
X-Google-Smtp-Source: ABdhPJynGJaZt+2MBTGQbv5h/Ft0b7o9vwMZTQdXo06B6WisTz2Amgy+iZaaunYwq2myCw2fVDooV5WMmxm5+SqWJeQ=
X-Received: by 2002:a2e:808a:: with SMTP id i10mr45178ljg.427.1604543613913; Wed, 04 Nov 2020 18:33:33 -0800 (PST)
MIME-Version: 1.0
From: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Wed, 04 Nov 2020 18:33:23 -0800
Message-ID: <CAP=vD9sr5bmzusfMcX-sgJAdz9nMiv6sni4dAim1kKdJgZfppw@mail.gmail.com>
To: IETF oauth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000224ceb05b352ecf7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/5CZAJQWDbI2OVFX-8KCQ3zQHPrc>
Subject: [OAUTH-WG] oauth par - authorize request with client_id
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, 05 Nov 2020 02:33:38 -0000
Hi all! A while ago I implemented draft 00 of this spec: - https://tools.ietf.org/html/draft-ietf-oauth-par-04 Now, in draft 04, I see that a request to the /authorize endpoint is defined with client_id and request_uri. The client_id was added since draft 00 (see: https://tools.ietf.org/html/draft-ietf-oauth-par-04#section-4). I am not sure if 'client_id' is now required, that's all. Thanks for clarification, regards, Sascha
- [OAUTH-WG] oauth par - authorize request with cli… Sascha Preibisch
- Re: [OAUTH-WG] oauth par - authorize request with… Takahiko Kawasaki
- Re: [OAUTH-WG] oauth par - authorize request with… Sascha Preibisch