This page gives a global overview of the structure of the CORE module of the OMS system, for more precise design please see below:
| Page tree | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Core goals
The goals of the CORE module is to provide a stable (backend) base for all other services to integrate with and rely on. the core will handle basic member storage, grouping, authentication and editing, as well as providing similar tools for groups created (bodies), on top of this it has integrated supports for oAuth 2.0 authentication such as with Microsoft Office 365. Additionally the core allows a new user to sign up, apply, for AEGEE and link that user to a member object when desired. The core will set up a permission system to be extended upon by the other microservices. The core will not handle the registration, routing, and enabling/disabling other microservices. While at this time of writing the core repository includes a frontend, the endgoal is to have this separated from the core, and let the real core microservice be a backend service solely.
...