Setting up the authentication backend
There are multiple ways of setting up the authentication backend of your application. It's common to see the user data being stored inside the main application itself. However, this approach is not scalable. The users stored directly inside the application will only be valid within the context of this application. So, if your estate has multiple applications, it will be problematic to authorize all of them with a single login.
An alternative approach is to use a separate authorization provider that all applications will integrate with. This way, when the user logs in, a token is issued to the user that is then stored in the session. Then, this user is free to access any other application until they log out or the token expires due to inactivity. This system is known as SSO.
When you use SSO, your authentication information will not be stored in any of the user-facing applications. Instead, there will be a dedicated application that will...
