[OAUTH-WG] Dealing with oAuth redirect_uri in draft-parecki-oauth-v2-1 and need for AS back channel initiation endpoint
Francis Pouatcha <fpo@adorsys.de> Wed, 08 April 2020 22:01 UTC
Return-Path: <fpo@adorsys.de>
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 C4F9E3A1866 for <oauth@ietfa.amsl.com>; Wed, 8 Apr 2020 15:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=adorsys.de
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 cyg7By2-vetw for <oauth@ietfa.amsl.com>; Wed, 8 Apr 2020 15:01:17 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 80AE33A1860 for <oauth@ietf.org>; Wed, 8 Apr 2020 15:01:17 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id j17so6359171lfe.7 for <oauth@ietf.org>; Wed, 08 Apr 2020 15:01:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adorsys.de; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=beQExBkz+RNMxK5LetOkWXDEMHZyeL7o5FaqqurKyXw=; b=fwuwmhR/YPd3cZ3A0zy/hwZTCAcDi0QeUQtOvhlYbMCn6hp4N5Xg6qHDZVhm4P+zcA jIybd1r0sSqj2A/nidsxvonwL8Kbofi26OwwkkhZWaSQ7Om5pkXuw4pGd1arOMUsKF+/ pbhzmafbizaunhJpA3YaUk5xo/IPvjnr6vbv0=
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:cc; bh=beQExBkz+RNMxK5LetOkWXDEMHZyeL7o5FaqqurKyXw=; b=ZnEu8m4vskKvtp7R1tX++GGBIwYzsFT12/AvIuczaEs9zA9U/8XDs7vf3z6UJzNGrO zVs8ISh5Yz9ev5Gd0a113xFTa7jJHnNtNbHNe4t2UoJf4i+Dtp6/7F/C+r5AzUerNrlU PJzjBfW4rCOAPZ/44PiP6ua6asPrIx2hfW+j3DN/GNyZP76sfjMkdH3b0eTK0Vg1JrZW p/NDwKvzBHfU7J0WJcNTolfom1jxVQ4Lwk+96DkqmhW2kTNnkXj38Dq0KrPXZCxKi9SV BtJnNvbRvO+LaH7s9kz9HwWEbtLGIKs51ldyCwhV2x8n/XyA2dGLMuZnpcKoHjzLxGQE EKNw==
X-Gm-Message-State: AGi0PuaY+ZF0y5iY4g5RLdh65/oqeYYaI21Oi1vohEIEoHei+pPS7BOv iFFaYGmsoAoNk8ajfWMDIoaEiHkt0KtuyZ1Jp9GME2f7nryROA==
X-Google-Smtp-Source: APiQypIXwgbYZEt3Pqgvn35ZsSzmV31SwUPk6Y6ian3zekg+htIRy+TPtdaVuiLLldDEjDNOR2Fk2JMuuenzSRqWbxI=
X-Received: by 2002:a05:6512:308e:: with SMTP id z14mr5930290lfd.110.1586383275306; Wed, 08 Apr 2020 15:01:15 -0700 (PDT)
MIME-Version: 1.0
From: Francis Pouatcha <fpo@adorsys.de>
Date: Wed, 08 Apr 2020 18:01:04 -0400
Message-ID: <CAOW4vyNZXnLXpkpO+oczFpZ_kRZvz8mCQKQ7FqrY+QUxE+n+ow@mail.gmail.com>
To: oauth@ietf.org
Cc: draft-parecki-oauth-v2-1@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009a4cba05a2cea30a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/oXOaB-4Vb7vO0tlEpb4HsPNn9b8>
Subject: [OAUTH-WG] Dealing with oAuth redirect_uri in draft-parecki-oauth-v2-1 and need for AS back channel initiation endpoint
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: Wed, 08 Apr 2020 22:01:20 -0000
There is a lot of effort associated with the handling and correct validation of a redirect_uri sent to the AS as part of the front channel authorization request, as this gets transported by user agents. The draft-parecki-oauth-v2-1 as a replacement of RFC 6749 must make sure redirect_uri is only sent to the AS through the back channel. This of course requires the implementation of a new "authorization request initiation endpoint". The draft-ietf-oauth-par-01 provides a guidance on how to design this initiation endpoint. -- Francis Pouatcha Co-Founder and Technical Lead at adorys https://adorsys-platform.de/solutions/
- [OAUTH-WG] Dealing with oAuth redirect_uri in dra… Francis Pouatcha
- Re: [OAUTH-WG] Dealing with oAuth redirect_uri in… Aaron Parecki
- Re: [OAUTH-WG] Dealing with oAuth redirect_uri in… Francis Pouatcha
- Re: [OAUTH-WG] Dealing with oAuth redirect_uri in… Justin Richer