📄️ Introduction
This component is the only component accessible to apps. All other components of the system (except for a part of View Manager component) will be on a hidden private network. This allows all the other components to communicated with each other with http requests instead of setting up https.
📄️ Schemas
Auth Service component needs to have access to the database and it registers multiple schemas:
📄️ New App Setup
The whole admin part is currently utilised by the Control Centre admin frontend component of the storage system. To read more about it, click here.
📄️ Profile Registration
After your app is set up and has jwtTokenForPermissionRequestsAndProfiles correctly saved, it can proceed to create a new profile.
📄️ Permissions
Before continuing, your app needs to have profiles sorted out. In other words, if it needs to work with a completely new type of events, it first needs to notify the system of that new type of event. If the app just wants to process some existing events, you already should know, you don't need to do anything.
📄️ Events Handling
Even though you probably know that Data Storage component is responsible for handling events, this Auth Service component adds additional layer of security by introducing authentication and authorisation for events handling.
📄️ Views Handling
View Templates and View Instances are trully being handled by View Manager component. Auth Service only checks whether the app is authorised to use given View Instance and then delegates this request to View Manager component. To know more about it, head over there, please.
📄️ Setup and Deployment
Please read this README for the latest Setup and Deployment of this component. We didn't want to copy the same information here.