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:09:15 +02:00
parent 797e9f54d2
commit 90a9b25533
Signed by untrusted user who does not match committer: yogsototh
GPG key ID: 7B19A4C650D59646
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
notes/customer_manager.org
View file

@ -51,6 +51,9 @@ But we could also use OpenID Connect, etc..
This could be the occasion to make a new global deployment.
A specific node with credentials that could be used to call all IROH nodes.
This could be challenging to make this fast, but this open the notion of
/Customer Manager Session/ at the User-Identity level.
** Long term Customer Manager
*** Reflections
@ -68,7 +71,7 @@ After different discussion we assume that:
It looks assumed in the documentation that MOST user domain email will be
enough to determine who is the customer that a user identity belongs to.
But it doesn't look like we will stop supporting non 3rd party IdP login?
It doesn't look like we will stop supporting non 3rd party IdP login?
So it means the we already have a design-space complexity.
@ -77,6 +80,7 @@ Without 3rd party IdP login we could imagine a user could belong to
multiple Customers. I think we should assume, for sake of simplicity that
this should not be the case, and our customer control access to their
platform via providing (or not) an email using their own domain name.
*** Customers
We need to build a single world wide API which would handle the