Define the scope of this project #2
Labels
architecture
There's no spec yet, or a functionality which requires changes to some other functionalities
needs-decision
This project, which is an identity and access management system, has core domain which is authentication and authorization.
We need to define what is identity. Is it including stuff like, e.g., profile images, contact info? Or should this project strictly manage entities required for authentication and authorization?
There are two directions for this project: strictly authentication & authorization, and generalized identity management system.
The most visible effect out of the project scope definition is how will we accommodate OpenID Connect: built into the core of this project, strong integration (the core provides abstractions and implementations through plug-ins or other mechanisms), or weak integration (e.g., through URLs).
The text was updated successfully, but these errors were encountered: