The app still requires the user to enter a DHIS2 server, username, and password, which as previously mentioned is less secure than using the existing session connected to the DHIS2 instance where the app is installed. It would be much better to remove the dhis2 configuration and just request data directly from the local DHIS2 instance. If communicating with an external DHIS2 server it is strongly recommended to support and prefer Personal Access Tokens instead of usernames and passwords.
cc @silviaemorreale @metabig
The app still requires the user to enter a DHIS2 server, username, and password, which as previously mentioned is less secure than using the existing session connected to the DHIS2 instance where the app is installed. It would be much better to remove the dhis2 configuration and just request data directly from the local DHIS2 instance. If communicating with an external DHIS2 server it is strongly recommended to support and prefer Personal Access Tokens instead of usernames and passwords.
cc @silviaemorreale @metabig