Re: [OAUTH-WG] client_id in PAR and JAR

Thiloshon Nagarajah <thiloshon@wso2.com> Tue, 30 June 2020 08:15 UTC

Return-Path: <thiloshon@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 B5A4C3A10E0 for <oauth@ietfa.amsl.com>; Tue, 30 Jun 2020 01:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level:
X-Spam-Status: No, score=-1.088 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, GB_FINANCIALSOLUTION=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 txBlWM3pCD2I for <oauth@ietfa.amsl.com>; Tue, 30 Jun 2020 01:15:33 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 454123A0F08 for <oauth@ietf.org>; Tue, 30 Jun 2020 01:15:32 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id e197so5653158yba.5 for <oauth@ietf.org>; Tue, 30 Jun 2020 01:15:32 -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 :cc; bh=QQj6DMACEDwYfWSWRybk4Mp4s9193pUGOH6W/8NnuDo=; b=YhX1sfBvDyNWsa6WP1hRLIK/SzUf6J88B0ofsbcFz5sZdceW98j/hQxjRx1xYusFWG eQP/GlZ5PbrXh6zGZ2yyKnXccwTdIeeibFLvQkklDYKaI8QyOC/9A7qNzjdPE7edDFG9 Eh5loc9nXc4PdeoiMdls8EtyIOnfH7H3lbh6Q=
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=QQj6DMACEDwYfWSWRybk4Mp4s9193pUGOH6W/8NnuDo=; b=SSPjqpX5RiwLpKVZF976tPjKTs+cy0o7UcyBtkukT6jA06wyOkzW4xldxIZHsugqVg PBERUqlAWoBurcwel243zdBAQ8CpK7BEX7o9aKXqICSHeMyyA1ZFxXCTgeIeUcW2tGTs W2uH6yR1hOaujR+te+o8QcYkjGCQdrNXY4QUz7gQA+047V8jx13apXdWRUs6+5vjDGjh Ywz43otJqPf6HsTOjPPsKYxDPzIPWuPT70RqOj4Mz8NWdxc84p6bdQ24kRnV1EJUQSRd LAHR4mRvzxos1qNy33kdug3u9uIpBJ/pgTlt+qJtWFBAHK1EVv9JJrhOjkULV0LTCHCc J16Q==
X-Gm-Message-State: AOAM532cCQbuLfnuf0FEi5DRdAnnzsDHMbSQ4/Kr+rhj2+iC92DGBtrh TwMGwEVEC/nRogT9wDhP61agDjrWYIg4gqcr6mFqsw==
X-Google-Smtp-Source: ABdhPJxot/TV8HGHn++qgYqq2VOy0U2/5CNkHld3sMftf79sAkjm76RUFdcq0OKAx1ga4g5GxcigXmFhwrC3pxBAGOc=
X-Received: by 2002:a25:37ca:: with SMTP id e193mr31638538yba.505.1593504931844; Tue, 30 Jun 2020 01:15:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAGObXPnr5tG6NXmhgOv_iKpjk+piXDiR+ZBse0ZYEuk1=3tRVQ@mail.gmail.com> <A2FA66BD-C352-4279-90C4-91663FB61BAE@gmail.com>
In-Reply-To: <A2FA66BD-C352-4279-90C4-91663FB61BAE@gmail.com>
From: Thiloshon Nagarajah <thiloshon@wso2.com>
Date: Tue, 30 Jun 2020 13:45:21 +0530
Message-ID: <CAGObXPmEU4t+Ku9dVn21VmjbVQWgMAfGKSaZR=1j-tZ9Q8YP4w@mail.gmail.com>
To: Filip Skokan <panva.ip@gmail.com>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000692f7605a948c7ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/hNGVntruHK1SXlQFWdF1NME3OJc>
Subject: Re: [OAUTH-WG] client_id in PAR and JAR
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: Tue, 30 Jun 2020 08:15:35 -0000

Hi Filip,

So I'm assuming client_id will be mandated as a query param in PAR as well?

Regards

On Tue, Jun 30, 2020 at 1:09 PM Filip Skokan <panva.ip@gmail.com> wrote:

> Hi Thiloshon,
>
> Not quite the way it went down but we have this adressed in a future PAR
> draft.
>
> Thank you ;)
>
> Filip
>
> Odesláno z iPhonu
>
> 30. 6. 2020 v 9:25, Thiloshon Nagarajah <thiloshon=
> 40wso2.com@dmarc.ietf.org>:
>
> 
> Hi All,
>
> In OAuth JAR specification, client_id is a required query parameter of
> authorisation call, in both *request* and *request_uri* flows [
> https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-23#section-5].
>
> But in OAuth PAR specification, which is a complimentary spec to JAR, it
> is specified "Clients are encouraged to use the request URI as the only
> parameter (in the authorisation call) in order to use the integrity and
> authenticity provided by the pushed authorization request." [
> https://tools.ietf.org/html/draft-ietf-oauth-par-01#section-4]
>
> Taking into account these both are building upon OAuth spec, which also
> mandates client_id query param in authorisation call, it seems like PAR
> is not compatible with OAuth and JAR specs.
>
> Is this intentional? If it is may I know the rationale behind this
> decision?
>
> Regards,
> --
> Thiloshon Nagarajah
> Software Engineer,
> Financial Solutions
> WSO2
> +94774209947
> <http://wso2.com/signature>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>

-- 
Thiloshon Nagarajah
Software Engineer,
Financial Solutions
WSO2
+94774209947
<http://wso2.com/signature>