This document talks about the coexistence strategy that is applied currently in the DIGIT platform where ERP modules are working alongside the Rainmaker product. This enables us to make any ERP module up and running with the Rainmaker product suite in minimal time.
Overview
.jpeg?version=1&modificationDate=1557827003484&cacheVersion=1&api=v2&width=663&height=400)
Technical details
This section will list some of the technical details of how each of the hooks is implemented in this coexistence framework.
Where does the user data reside?
All user data, be it citizen or employee will reside in the Rainmaker product. This data will be called from other systems (ERP finance or third-party system) for authentication purpose.
How does the login work?
Login will always happen from the Rainmaker system, where a user will enter the username and password and select the city name. The system will generate an auth token after the authentication is successful. This auth token is stored in the local storage.
When any ERP menutree links are accessed, the system will get this auth token from the local storage and pass it to ERP using a POST call using the hidden variable in the body. This auth token is stored in a hashmap in the Redis server along with the user id. When a second URL from ERP is accessed, the system will check if the auth- token coming as part of the request is the same as that of the auth-token available in the Redis server. If it is the same then the system allows proceeding with the transaction.