According to setup WebAPI for ATLAS, source_daimon as SQL file is designed to collect connection info also include username and password in format of database connection string. (as code below)
The connection string is somewhat currently contain sensitive information and host name should dynamically matched to container name for this case but currently was fixed string.
Current recommended approach is just expose default or simple username/password like this, but have additional work on access control/network segmentation.
Example:
Let ohdsi-webapi-pg of database not expose inbound connection from outside container, but still able to reach by other container, include container of DB management like pg-admin-web which allow to be reach from external and tighten credential on this level instated.
According to setup WebAPI for ATLAS,
source_daimonas SQL file is designed to collect connection info also include username and password in format of database connection string. (as code below)populate_source_source_daimon.sql
The connection string is somewhat currently contain sensitive information and host name should dynamically matched to container name for this case but currently was fixed string.
Current recommended approach is just expose default or simple username/password like this, but have additional work on access control/network segmentation.
Example:
ohdsi-webapi-pgof database not expose inbound connection from outside container, but still able to reach by other container, include container of DB management likepg-admin-webwhich allow to be reach from external and tighten credential on this level instated.