IETF Logo Mail Archive

Re: [OAUTH-WG] oauth par - authorize request with client_id

Sascha Preibisch <saschapreibisch@gmail.com> Thu, 05 November 2020 04:49 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 727953A16A2 for <oauth@ietfa.amsl.com>; Wed, 4 Nov 2020 20:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 PuxEWa87-Sw1 for <oauth@ietfa.amsl.com>; Wed, 4 Nov 2020 20:49:22 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 70B253A166A for <oauth@ietf.org>; Wed, 4 Nov 2020 20:49:22 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id s30so379931lfc.4 for <oauth@ietf.org>; Wed, 04 Nov 2020 20:49:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qnUkeCVsmY7iBRtMzRhG5Z2WMRe5Dl7CRw6j1wHXEz0=; b=NZ4kPkT3VnPJ1u+PPW+yTfpzVIgwJuvrCwNbt37/LrNbKPA3RSNEGdyjAro5fLFZ/4 AOxVE9qAKL6G4Rx6RHtuPTDUDYj2HxvXEVTiWggh/rsHHmIdDTiJ0fB09izIG3bxol+I Ib0uQMilwl2EJEVYFK5xtURRWQPEJ3yT+YCcRmUYBa77G8wUZg5oMFaZ7EhSQ9fXxTDZ tnHZP0iZHe8YIzfAIiU2hxY9+1+gFUfM1h3rhfsGs35PaJznmlooKQcU5roQOq0VvNJC 8KSG5UX+g5Em7g7cFUOY3GauyHl6kToBgU67ChMwrP1e2GuDU+MIs/clx1tdekBgcCS8 N3qw==
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:cc; bh=qnUkeCVsmY7iBRtMzRhG5Z2WMRe5Dl7CRw6j1wHXEz0=; b=rttgg38Lrks0NKFI59F/WHflTPzOMQkLt3BOJSzj46xMy4Pvif51yYtvXRLjzbo6pk W2MACFj+tUchEllIFHE9zYZYRjk3dS2Bp0lyHBUG1P8XFaCn4GtcVuO6edfJfWxoj0lV wQ/PIGYsfYt3JY+5+xMDcQC5JXjq3dXeXyjWK2fGiGbA30WZ/qDKLqbqgREHfZ4mtx82 auawfLALkZUUazEr5C95bB23ttkXbaF2TlX4l0latfJS61HE9gHFxhq6GlkD296RcZLp b8z2ZEVWz8dtmFz0NlUr2TVw4P9qfk4Kdw3xnW7x6+43Ty3uUztsWqpiuN8+xVRlMwol BY5A==
X-Gm-Message-State: AOAM530sD9XdAowk+DskW7zfZB00p4qpKcV+A7Ha+CjlyzOrDAHFGyoY 3h0kBdeYONnWpcsSwBHKS+PuOoUXK8EIh8Pvxn4=
X-Google-Smtp-Source: ABdhPJzbc5WW5owUAASo42uv1Blflx0ymTLX7mC32CM6bcN2P0PoIB8bSf3tZfWFLj4ytY1o+sgO+zdGXY6Gbs3b45A=
X-Received: by 2002:ac2:5ca5:: with SMTP id e5mr186639lfq.497.1604551760371; Wed, 04 Nov 2020 20:49:20 -0800 (PST)
MIME-Version: 1.0
References: <CAP=vD9sr5bmzusfMcX-sgJAdz9nMiv6sni4dAim1kKdJgZfppw@mail.gmail.com> <CAHdPCmOOQ4ZNEmGn2uUYH3VWKAPPXm8pTj0u4e1LuHEk1oy19g@mail.gmail.com>
In-Reply-To: <CAHdPCmOOQ4ZNEmGn2uUYH3VWKAPPXm8pTj0u4e1LuHEk1oy19g@mail.gmail.com>
From: Sascha Preibisch <saschapreibisch@gmail.com>
Date: Wed, 04 Nov 2020 20:49:10 -0800
Message-ID: <CAP=vD9vBXbrgd=kZt6Hb-K22X-b0b+awdQQEDMSVBQMyvbtnFQ@mail.gmail.com>
To: Takahiko Kawasaki <taka@authlete.com>
Cc: IETF oauth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b3650505b354d1a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/dtYnc1LNQOU1wpn3rjpUUIlEG_U>
Subject: Re: [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 04:49:24 -0000

Thank you, Taka!

I will check out the referenced document.

Regards,
Sascha

On Wed., Nov. 4, 2020, 19:15 Takahiko Kawasaki, <taka@authlete.com> wrote:

> Hi Sascha,
>
> The change you found in the draft 04 is the change made to the JAR (JWT
> Secured Authorization Request). Now, "client_id" is mandatory. I summarized
> technical details about JAR in the article below. It describes the reasons
> for the necessity of "client_id". PAR is mentioned there, too.
>
> Implementer's note about JAR (JWT Secured Authorization Request)
> https://darutk.medium.com/implementers-note-about-jar-fff4cbd158fe
>
> Best Regards,
> Taka
>
> On Thu, Nov 5, 2020 at 11:33 AM Sascha Preibisch <
> saschapreibisch@gmail.com> wrote:
>
>> 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 mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>

v2.23.0 | Report a Bug | By Email