Please enable JavaScript.
Coggle requires JavaScript to display documents.
Account v3.0 Scope of Arch (Permission Management (Exchange? (All origins…
Account v3.0 Scope of Arch
Exchange
Support - Basic
Security Storage is required
Static Authenticator is enough
Single Authenticator is enough
Single Instance is enough
Federated Credential
Support
Multiple Origin
is required
e.g. Email, Calendar share the token
2-1.
Permission Management
for Origins
Exchange
All origins could obtain password? By Origin name?
User Mediation
?
Google
Authorize token by Google Endpoint? Need to check
Facebook
Need to check
KaiAccount
All certified origin could obtain password
Multiple Authenticator
Support
e.g. Exchange, Google, Facebook
3-2.
Dynamic Authenticator
Support
Might be technical problem?
3-1. What
AccountTypes
Exchange
Static Authenticator
Facebook
SDK? webjs, might be technical problem
Google
Static Authenticator redirect Google Login Page
KaiAccount
Front-end need to implement Authenticator
User Mediation
Support
Enhanced Security
Complex Arch -> Need to maintain each Permission of Account
Need to Separate a UI Handler from Authenticator
Common Control
Support
SyncNow button
View the list of Account Types
e.g. Exchange, Google, Facebook
View the list of Logged In Instances
e.g. a@ gmail, b@ gmail
Multiple Account Instance
Support
e.g. a@ gmail, b@ gmail
Complex Arch -> Need to Divide Authenticator to Protocol Handler and Logged In Instance
Permission Management
Exchange?
All origins can obtain password?
KaiAccount
All certified origins can obtain token
6-1. Exchange, Google, KaiAccount
has their owned rule of Permission Management
and Authorize Module
Google
Permission should be authorize by Google Backend
Pre-defined whitelist
Background process died on Authenticator