Re: [OAUTH-WG] PAR error for redirect URI?

Filip Skokan <panva.ip@gmail.com> Thu, 03 December 2020 10:17 UTC

Return-Path: <panva.ip@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 509EB3A0E27 for <oauth@ietfa.amsl.com>; Thu, 3 Dec 2020 02:17:09 -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=unavailable 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 qTgtskVkUJIi for <oauth@ietfa.amsl.com>; Thu, 3 Dec 2020 02:17:06 -0800 (PST)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 E5EFC3A0B95 for <oauth@ietf.org>; Thu, 3 Dec 2020 02:17:05 -0800 (PST)
Received: by mail-yb1-xb2c.google.com with SMTP id g15so1526371ybq.6 for <oauth@ietf.org>; Thu, 03 Dec 2020 02:17:05 -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=VxpWKglMKgTg3riMq0wgSV2uzjktNL4l6lnbZwLPCA8=; b=u24eblngJ0ukj7b0FNqV0o5raA/Po5IrhEZZEkZterLn/j0LA/TCSWcgRv6WRdsfu7 DYVHCmC0xRcb8er+1pXMPgAVkWq8bgUFnzc9mfgIPm3DFsvAaxTY/8J+7kMX2xbFvKG1 pxFgraNk5+68+h5FxdHZS0HwEqvYpUzW/zK4FE71b3L+VyuQ5VEc81Xv3v0bLJaiDDKe lbPn7Okj70C/i4rk/JPE9I8B0bZXtMyNi4YcRgJNqHGZHUwEp5xyrqX8QtMOp3xk637w +feEFy0vIHnI8QcRf77XAGw3D5o3Xi1gBMT5e6WrHiWCv4sWZWPC3aCe0I1an1apihrX Lj9Q==
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=VxpWKglMKgTg3riMq0wgSV2uzjktNL4l6lnbZwLPCA8=; b=gacmpOlq8DQb0AVcqZwGIwPFyrgXH5cPYYf5uYdzYhz++VDXSjixPATS01lV9b3J3q FSurb06m+IzSKY2aWiEicfyjEuFWhTSUUWtcMorgOk0nRVBbqiUXrRBvyFe9ZcAtn491 6Jm7Ca+n5Kmf5RaoMSamRpo6vMYseuwDvMpdqOWFXSo85+IKJ5im5qdADxiYXay3zazx Cxdz+w93+GQzH8pHlbvE4sxv/jkwc2jQxsBQR1msFLEjEBG+5WawpUkm/1jJFCz7K4RD fPTfml0hifZo/nfYA7MP3EKJROp4JzgxslYqK2EuDfUoLXkxa59RHeSwIyH7GPaz9bM+ dvMg==
X-Gm-Message-State: AOAM531aDHJlJ1/I5hVh8YyB6YUmbE4xjxbjc/ziIj8AZ0slu1E3qVDg yvSuu2uTGks3gmywLJGuahBVaqB7xhxRbXYkJw==
X-Google-Smtp-Source: ABdhPJxAODK4ebJzFLIDarl8+Rq57e4tw3Yq6PueWSR/H0Sy19QeiE06Fkj8OVghcqxu9kIFtLSNX01MrJj3W1BZ/og=
X-Received: by 2002:a25:2e4e:: with SMTP id b14mr3502035ybn.259.1606990625139; Thu, 03 Dec 2020 02:17:05 -0800 (PST)
MIME-Version: 1.0
References: <CA+k3eCQitAWnHaw2zz0jwyjHxWPYe0VPct1Op1T13BVhydkXDQ@mail.gmail.com> <CALAqi__ncGQgbunhunmaCrtUsAe-v+HnLWZM2Ca5VWarUr2Y=w@mail.gmail.com> <CDA006E7-8D4F-49AF-9C68-3BCEEFCFA687@lodderstedt.net>
In-Reply-To: <CDA006E7-8D4F-49AF-9C68-3BCEEFCFA687@lodderstedt.net>
From: Filip Skokan <panva.ip@gmail.com>
Date: Thu, 03 Dec 2020 11:16:29 +0100
Message-ID: <CALAqi_9ewvmUUJNzXMU2JUU9eSVwwjGQMe7mCva=WFrA1JME9g@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Cc: Brian Campbell <bcampbell=40pingidentity.com@dmarc.ietf.org>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005e6fa105b58ca936"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/P_m456Ey0rD5UkLAKlet6AUad48>
Subject: Re: [OAUTH-WG] PAR error for redirect URI?
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, 03 Dec 2020 10:17:09 -0000

To be clear, I'm not advocating to skip the registration, just wanted to
mention a potential concern. If the process allows it and it will not
introduce more delay to publication, I think we should go ahead and
register the error code.

Best,
*Filip*


On Thu, 3 Dec 2020 at 11:06, Torsten Lodderstedt <torsten@lodderstedt.net>
wrote:

>
>
> > Am 03.12.2020 um 09:56 schrieb Filip Skokan <panva.ip@gmail.com>:
> >
> > There are several documents already mentioning "invalid_redirect_uri" as
> an error code, specifically RFC7519 and OpenID Connect Dynamic Client
> Registration 1.0. But these don't register it in the IANA OAuth Extensions
> Error Registry, presumably because they're neither for the authorization or
> token endpoints.
> >
> > While I think it'd be great if we had this error code registered, I also
> worry that its registration could confuse implementers to think it's okay
> to return it from the authorization endpoint.
>
> I understand your concern. On the other hand, registering the error code
> is in my opinion the proper way forward. The registration is scoped to a
> usage location, should be pushed authorization endpoint then, and RFC6749
> gives clear guidance on how to treat errors related to the redirect URI at
> the authorization endpoint.
>
> "If the request fails due to a missing, invalid, or mismatching
>    redirection URI, … authorization server ... MUST NOT automatically
> redirect the user-agent to the
>    invalid redirection URI."
>
> I think if an implementor ignores this, it will ignore any advise.
>
> best regards,
> Torsten.
>
> >
> > Best,
> > Filip
> >
> >
> > On Thu, 3 Dec 2020 at 00:29, Brian Campbell <bcampbell=
> 40pingidentity.com@dmarc.ietf.org> wrote:
> > During the course of a recent OIDF FAPI WG discussion (the FAPI profiles
> use PAR for authz requests) on this issue it was noted that there's no
> specific error code for problems with the redirect_uri (the example in
> https://www.ietf.org/archive/id/draft-ietf-oauth-par-04.html#section-2.3
> even shows a general error code with mention of the redirect_uri not being
> valid in the error description). Some folks on that call thought it would
> be worthwhile to have a more specific error code for an invalid
> redirect_uri and I reluctantly took an action item to raise the issue here.
> At the time I'd forgotten that PAR had already passed WGLC. But it's been
> sitting idle while awaiting the shepherd writeup since mid September so
> it's maybe realistic to think the window for a small change is still open.
> >
> > Presumably nothing like an "invalid_redirect_uri" error code was defined
> in RFC 6749 because that class of errors could not be returned to the
> client via redirection. But the data flow in PAR would allow for a
> "invalid_redirect_uri" so it's not an unreasonable thing to do.
> >
> > As I write this message, however, I'm not personally convinced that it's
> worth making a change to PAR at this point. But I did say I'd bring the
> question up in the WG list and I'm just trying to be true to my word. So
> here it is. Please weigh in, if you have opinions on the matter.
> >
> >
> >
> > CONFIDENTIALITY NOTICE: This email may contain confidential and
> privileged material for the sole use of the intended recipient(s). Any
> review, use, distribution or disclosure by others is strictly prohibited.
> If you have received this communication in error, please notify the sender
> immediately by e-mail and delete the message and any file attachments from
> your computer. Thank you._______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> > https://www.ietf.org/mailman/listinfo/oauth
> > _______________________________________________
> > OAuth mailing list
> > OAuth@ietf.org
> >
> https://www.google.com/url?q=https://www.ietf.org/mailman/listinfo/oauth&source=gmail-imap&ust=1607590629000000&usg=AOvVaw3aW1gdv4EEiLmNYzlsJj-A
>
>