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

Warren Parad <wparad@rhosys.ch> Sun, 14 February 2021 13:53 UTC

Return-Path: <wparad@rhosys.ch>
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 56ECB3A0C30 for <oauth@ietfa.amsl.com>; Sun, 14 Feb 2021 05:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level:
X-Spam-Status: No, score=-0.188 tagged_above=-999 required=5 tests=[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, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rhosys.ch
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 zfZu_XkYpMWu for <oauth@ietfa.amsl.com>; Sun, 14 Feb 2021 05:53:33 -0800 (PST)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 B23B43A0C2F for <oauth@ietf.org>; Sun, 14 Feb 2021 05:53:33 -0800 (PST)
Received: by mail-io1-xd2d.google.com with SMTP id f6so4190175ioz.5 for <oauth@ietf.org>; Sun, 14 Feb 2021 05:53:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rhosys.ch; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uVCGfFQDl7ZluxXnMe1EsedBVuL03fHnlX5/CjzneIc=; b=KruT/SQwzmK5NXbkX0sNJOlVsG+LEqmvPp3lXgxE+2Z4sRAb+eBX3rt3luSj/IeQWI Ob7tWoxW6kZ8DpoZ/haTSp8gYHEjeu9fcwRLiATF6Dqr1s8JHPhasmdMxo3Tmh7nZWwY kPhe4cEFMyLwnXvDx0GhtXbp3EdKhW8kpNpqgFVSUfDc0IKu2UMurCqqjls7JoVeEigQ O/vnvIqDmW7mXgc5+NkGl6+j5sLBMgQnOr0RY+3jr8Pv6M1kyYxmlb9zWAPzpIAdGx3R pmUEJrMpWQ14SiE5/w1kLMfmenQE5JFt59OcL7GYbIgarXvvIabqzLigPbrwtOHnhKrs QxQA==
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=uVCGfFQDl7ZluxXnMe1EsedBVuL03fHnlX5/CjzneIc=; b=MwHzGYlzbm4bxGbZgoHbDoTM+xrxy38kvYWX+vgyANEEnn//UPhVKwKa/cjUkxWAyx KIYNBTHuKVI0pSbrIg+BklyZYxuhBc3FbWq4gIUrk5yUbm1kGZIjfyGOeQfrwRx51tbX LCBo7cGCWNLImYTUMW/b6PkGArJIPP7gqik8/k6YF/dVyvohXmjOOTjKZRcufwkvsfHg 8YCdMnVZFwVuE62QV6jQI/2DGTTLKT/CPuE9qj1Hao1w82jxXgZ0vR3OeZKtTBhCPUQ+ XVPgei4A87Y0N6lWDnZC/99fUUB9Uf677DA9BguoZ5dTzFxeddVOJNC4Z154ZPrU2/dR 8/kw==
X-Gm-Message-State: AOAM531J8AHNFtB6GMtrvPxI0EpZOCZqILVCryus9r+wnlm7x/iAGTYn +u8Oh/MbV8odWMs6VdMuNdgXsNuTmy0WULiIZr70
X-Google-Smtp-Source: ABdhPJxHOzQDBeSYznbutNLWu7wp0+T9Ca3vkLmPssKlAbH/tk7+h9/HJL2psMVob0HnvnWxTJqPb0TDddCKd6Vo3YU=
X-Received: by 2002:a02:661c:: with SMTP id k28mr10941870jac.78.1613310812692; Sun, 14 Feb 2021 05:53:32 -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> <CAGL0X-qvLz=gG06Q3mL5yNs5f-eqSwxO-g=K=cDKdmC8VP+UEg@mail.gmail.com>
In-Reply-To: <CAGL0X-qvLz=gG06Q3mL5yNs5f-eqSwxO-g=K=cDKdmC8VP+UEg@mail.gmail.com>
From: Warren Parad <wparad@rhosys.ch>
Date: Sun, 14 Feb 2021 14:53:21 +0100
Message-ID: <CAJot-L3AUd-kYuw4jByJqG85DCJ-9XRjA6A53Dm8h3Q+vTNZnw@mail.gmail.com>
To: Stoycho Sleptsov <stoycho.sleptsov@gmail.com>
Cc: Vittorio Bertocci <vittorio.bertocci@auth0.com>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e73ca905bb4c3131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/jbOETOkOyW4MpSMiB-8O2-nGvyc>
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:53:35 -0000

Why doesn't PKCE help for authentication?

Warren Parad

Founder, CTO
Secure your user data and complete your authorization architecture.
Implement Authress <https://authress.io>.


On Sun, Feb 14, 2021 at 2:48 PM Stoycho Sleptsov <stoycho.sleptsov@gmail.com>
wrote:

> 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.
>