Re: [OAUTH-WG] Token Mediating and session Information Backend For Frontend (TMI BFF)

Stoycho Sleptsov <stoycho.sleptsov@gmail.com> Sun, 14 February 2021 13:48 UTC

Return-Path: <stoycho.sleptsov@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 DE6F13A0C18 for <oauth@ietfa.amsl.com>; Sun, 14 Feb 2021 05:48:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[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] 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 2yoe7qYx1dv3 for <oauth@ietfa.amsl.com>; Sun, 14 Feb 2021 05:48:17 -0800 (PST)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 7B03E3A0C11 for <oauth@ietf.org>; Sun, 14 Feb 2021 05:48:17 -0800 (PST)
Received: by mail-ej1-x62a.google.com with SMTP id u18so4924053ejf.6 for <oauth@ietf.org>; Sun, 14 Feb 2021 05:48:17 -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=tFZdd9hNoCLK0UlUmGMV1IftCzRuJ+kx+/lK58TKoBs=; b=ZQWkOE7lVBSKcMF6P8DVyB7s1CpTzTPIERCNi1LCCWKenIaSXHIx9zF9aE//bDFQ+w zh8iIQSQO5WcpA6qdd9Mw2iUA4vFvfg2jLkSBQHVX7FdtJXCjrItBtl+O9HkTB4FzFuQ R6VhRsCqU3339eNC1ts4LR5RlJCD1sMkX7JPRnMWs1MMFYwWI/oIWelPdMAuI9nPR03c oXRcxVEz/cbFfngqCOpB9aAbpe3zLt50FA23XxsOvqAWCHYn/e84urfX4SAaRWngewFm nSEq3BoFYAvBaGNkn3YG/OKxTu6A6PARHyL9Xm/MVz8W9sVYB3Y9sUtQWULef4e71w7a /ccw==
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=tFZdd9hNoCLK0UlUmGMV1IftCzRuJ+kx+/lK58TKoBs=; b=gMcvaiI5IIckFtOQrInhaGiAOH4W8jcJcasR35dQjWs4Om+sO5uZznuoRCZJLdpj5j bcm9FOf1uxvv+B0cqfov0s0g5mPeW7348tMbePXt+pwxQVYqsIjbpLyKBwYLYRGFEx3z 14CkWlKThGl2zpvmEz9KIU7433jkK+PhFDjrCWwWOR4WZ+AcGJchyRYsrJpNcq3V1XN+ F7MKKqx/nk06Pnb+GUI24ruMbP6/lWtNAIj2du+uBPqtVdyZJ7TO+QnZPyrl3/dkzbnr haRucqrlqw9OxpALmQf+SiFZVs7x7nc4dpT226nRq4MTSihA11airFGUzGq3osuVrUhc cxRg==
X-Gm-Message-State: AOAM533416DQ6OgFT272On9tUeSIhjUb8ee3/LUn9KVy0D79Q6rfR/Qa jSkoGHr+3EeEQzo1r7oqlbGfXbTNoOXSeo3AadI=
X-Google-Smtp-Source: ABdhPJwwENg2PvGSoVqu8nWmTgXQZGnKH3eNkpsfHMbTkVo+UmdQZ+sE4dLxf0Iv7AACMPhmfnVgoN+xe7kjvOtj/K8=
X-Received: by 2002:a17:906:33c5:: with SMTP id w5mr11621329eja.319.1613310495581; Sun, 14 Feb 2021 05:48:15 -0800 (PST)
MIME-Version: 1.0
References: <CO6PR18MB4052805653BFECD35E8A0E66AE8B9@CO6PR18MB4052.namprd18.prod.outlook.com> <C741095F-8350-4531-BFA4-4AAE929C08C3@forgerock.com> <CAJot-L1xJFgBkTjKti1LmEkrMZ56SkpuwpTN+Q7MTNZF7aQ01Q@mail.gmail.com> <CO6PR18MB405236B3F50E3A5C42B82C39AE899@CO6PR18MB4052.namprd18.prod.outlook.com>
In-Reply-To: <CO6PR18MB405236B3F50E3A5C42B82C39AE899@CO6PR18MB4052.namprd18.prod.outlook.com>
From: Stoycho Sleptsov <stoycho.sleptsov@gmail.com>
Date: Sun, 14 Feb 2021 15:48:04 +0200
Message-ID: <CAGL0X-qvLz=gG06Q3mL5yNs5f-eqSwxO-g=K=cDKdmC8VP+UEg@mail.gmail.com>
To: Vittorio Bertocci <vittorio.bertocci=40auth0.com@dmarc.ietf.org>
Cc: Warren Parad <wparad=40rhosys.ch@dmarc.ietf.org>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000000695905bb4c1f15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/f5WdSZjGuoJe1-1OYbfOrruzIok>
Subject: Re: [OAUTH-WG] Token Mediating and session Information Backend For Frontend (TMI BFF)
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: Sun, 14 Feb 2021 13:48:19 -0000

I would like to add my reasons about the "Why are developers creating BFF
for their frontends to communicate with an AS",
with the objective to verify if they are valid.

I need the client app. to be authenticated at the AS (to determine if it is
a first-party app., for example).
If we decide to implement our client as a frontend SPA , then we have no
other option except through a BFF, as PKCE does not help for authentication.

Or is it considered a bad practice to do that?

Regards,
Stoycho.