yogsototh/deft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

notes/customer_manager.org

Browse source
This commit is contained in:
Yann Esposito (Yogsototh) 2021-10-15 15:50:03 +02:00
parent 56db79f5c9
commit 6b6a07c286
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
notes/customer_manager.org
View file

@ -81,13 +81,15 @@ notion of /Customer Manager Session/ at the User-Identity level.
Also the claims will be different. Also the claims will be different.
The claims will not contain any =user-id= nor =org-id=, but only The claims will not contain any =user-id= nor =org-id=, but only
=user-identity-id= and probably =idp-id= (not sure). =user-identity-id= and probably =idp-id= (not sure).
- [ ] Create a new set of services in IROH that will be the future Customer - [ ] 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 Manager. And see with the ops how we could deploy it.
deploy this on NAM, and the node will call the 3 IROH nodes. I would guess deploy this on NAM, and the node will call the 3 IROH nodes.
*** Organization managements 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. 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 Typically one step could be a way to control the orgs from this centralized