Comment on page
It is important to choose strong unique passwords before a deployment, even more so if it contains real data or if it is exposed to the internet.
In each compose profile you will find a
.envfile containing configuration options. Among them are the passwords to be set. Note that most of those passwords configured that way will only work on a fresh database. Example:
POSTGRES_PASSWORDconfigures the password for the
postgresadministration user of the PostgreSQL database.
PGADMIN_PASSWORDconfigures the password for the
adminuser of the PgAdmin web interface. Note that it is necessary to set it only if your deployment profile deploys this tool.
KEYCLOAK_PASSWORDconfigures the password for the
keycloakadministration user of the default
masterrealm of Keycloak.
As of v1.0.0, the provisioning of the configuration of Keycloak has changed and this setting is not effective. After the initial deployment, you must login to the administration interface with the default password (
keycloak) and change it.
I2B2_WILDFLY_PASSWORDconfigures the password for the
adminuser of the wildfly instance hosting i2b2.
I2B2_SERVICE_PASSWORDconfigures the password for the
AGG_SERVICE_ACCOUNTuser of i2b2, used to operate background automated tasks by the i2b2 services.
I2B2_USER_PASSWORDconfigures the password for the default
demousers used by MedCo.