IETF Logo Mail Archive

Re: [OAUTH-WG] Recommended OpenId Connect Flow for SPA with Microservices

David Sautter <david.sautter@web.de> Mon, 22 July 2019 13:54 UTC

Return-Path: <david.sautter@web.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 010741202CD for <oauth@ietfa.amsl.com>; Mon, 22 Jul 2019 06:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Level:
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 mLyByDbqZI8n for <oauth@ietfa.amsl.com>; Mon, 22 Jul 2019 06:54:56 -0700 (PDT)
Received: from outgoing.selfhost.de (outgoing.selfhost.de [82.98.87.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AE61120282 for <oauth@ietf.org>; Mon, 22 Jul 2019 06:54:56 -0700 (PDT)
Received: (qmail 4428 invoked from network); 22 Jul 2019 13:54:52 -0000
Received: from unknown (HELO ?172.28.23.85?) (postmaster@davidsautter.de@80.246.32.28) by mailout.selfhost.de with ESMTPA; 22 Jul 2019 13:54:52 -0000
Date: Mon, 22 Jul 2019 15:54:51 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <D5171CFB-3188-4153-9728-D91AFF12536A@lodderstedt.net>
References: <f9e47830-744b-e358-2b13-2bd7de75c513@web.de> <503669B0-8DCD-4811-8B69-0CE0F4E0D8B0@alkaline-solutions.com> <D5171CFB-3188-4153-9728-D91AFF12536A@lodderstedt.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----B0SEU07GJ2Y1FQDWV34AFLF3WGX78W"
Content-Transfer-Encoding: 7bit
To: Torsten Lodderstedt <torsten@lodderstedt.net>
CC: OAuth WG <oauth@ietf.org>, David Waite <david@alkaline-solutions.com>
From: David Sautter <david.sautter@web.de>
Message-ID: <7900405B-FAF8-4210-B349-C5DA4D8D8E59@web.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/bT-NFJ-4bXEgIWT_qvMpn8PQg4Q>
Subject: Re: [OAUTH-WG] Recommended OpenId Connect Flow for SPA with Microservices
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: Mon, 22 Jul 2019 13:55:02 -0000

Hi Thorsten,

do you mean that for service2service communication or for the frontend to backend communication?

How would that process look like in a nutshell?

Thanks!
David



Am 22. Juli 2019 14:30:41 MESZ schrieb Torsten Lodderstedt <torsten@lodderstedt.net>:
>Hi David, 
>
>> On 12. Jun 2019, at 04:01, David Waite <david@alkaline-solutions.com>
>wrote:
>> 
>> To prevent exfiltration, the options are limited. 
>> - Token Binding will work, but only currently has support in Edge.
>> - Mutual TLS will work, but has a poor experience unless you are
>deploying alongside group policy.
>> - DPoP was written specifically for the browser use case (such as
>letting you use WebCrypto for non-exportable tokens). It is an early
>draft but has some initial implementations already.
>
>If you use a backend to relay or orchestrate your micro service
>interactions, mTLS (with self-signed certs) is the easiest choice from
>my perspective. 
>
>kind regards,
>Torsten. 

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

v2.46.0 | Report a Bug | By Email | System Status