From 6b6a07c2861658478f21f102e8830a4ee6c1f802 Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Fri, 15 Oct 2021 15:50:03 +0200 Subject: [PATCH] notes/customer_manager.org --- notes/customer_manager.org | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/notes/customer_manager.org b/notes/customer_manager.org index 5deea216..83b830cc 100644 --- a/notes/customer_manager.org +++ b/notes/customer_manager.org @@ -81,13 +81,15 @@ notion of /Customer Manager Session/ at the User-Identity level. Also the claims will be different. The claims will not contain any =user-id= nor =org-id=, but only =user-identity-id= and probably =idp-id= (not sure). - - [ ] Create a new set of services in IROH that will be the future Customer - Manager. And see with the ops how we could deploy it. I would guess - deploy this on NAM, and the node will call the 3 IROH nodes. -*** Organization managements + Manager. And see with the ops how we could deploy it. + I would guess deploy this on NAM, and the node will call the 3 IROH nodes. + This will be the occasion to test the latency between nodes and see if this + is not problem. +*** Organization managements Once we have a deployed a global node that + +could makes call to all IROH nodes. -Once we have a deployed a global node that could makes call to all IROH nodes. We could start to think about providing more and more API accesses. Typically one step could be a way to control the orgs from this centralized