...
Configuration is possible via docker environment variables (for supported parameters). An example for this configuration is described in section Provisioner - Docker.
VM based
LDAP Metadirectory
...
Codeblock |
---|
systemctl {start|stop|restart|status} slapd |
- Logs: TODO
To start the slapd server in debug mode use this command:
...
These log levels are supported:
More information about logging and debugging OpenLDAP can be found in the documentation: https://www.openldap.org/doc/admin24/runningslapd.html
...
Configuration is possible via docker environment variables (for supported parameters). An example for this configuration is described in section Provisioner - Docker.
VM based
The compiled frontend (Angular JavaScript app with assets like images, CSS-files etc.) is located in /var/www/didmos2lui and then shipped as static files using an Apache webserver. The following locations on the VM are used:
...
Configuration is possible via docker environment variables (for supported parameters). For a list of general environment variables refer to didmos2 Authenticator. An example for this configuration is described in section Provisioner - Docker.
VM based
didmos Auth is installed as a python virtual environment and deployed as a mod_wsgi app in Apache webserver. The following locations of the VM are used:
...
The logs can be accessed via docker logs (see list of general commands).
The composition of the container and basic configuration is done in the file docker-compose.yml.
Codeblock | ||
---|---|---|
| ||
ra: image: ${CUSTOMER_RA_IMAGE}:${CUSTOMER_RA_TAG} container_name: ${CUSTOMER}-ra depends_on: - rabbitmq volumes: - didmos2-ra-config:/opt/daasi/didmos2/ra/config/ environment: LDAP_URL: ${LDAP_URL} RA_LDAP_ACCOUNT_PW: ${RA_LDAP_ACCOUNT_PW} RA_SENDER_EMAIL: ${RA_SENDER_EMAIL} RA_DEFAULT_RECEIVER_EMAIL: ${RA_DEFAULT_RECEIVER_EMAIL} INIT_PARAM: -i 2 RABBITMQ_URL: ${RABBITMQ_URL} RABBITMQ_USER: ${RABBITMQ_USER} RABBITMQ_PW: ${RABBITMQ_PW} LDAP_ACCESSLOG_PW: ${LDAP_ACCESSLOG_PW} LDAP_MANAGER_PW: ${LDAP_MANAGER_PW} SMTP_HOST: ${SMTP_HOST} SMTP_USER: ${SMTP_USER} SMTP_PASSWORD: ${SMTP_PASSWORD} SMTP_PORT: ${SMTP_PORT} extra_hosts: - "host.docker.internal:host-gateway" |
Additional configuration Configuration is possible via docker environment variables (for supported parameters). These variables are referenced in the docker-compose.yml and set in the .env file:
Codeblock | ||
---|---|---|
| ||
...
LDAP_ACCESSLOG_PW=...
LDAP_MANAGER_PW=...
LDAP_URL=ldap://host.docker.internal:389
LDAP_BIND_DN="cn=manager,dc=didmos,dc=de"
RA_LDAP_ACCOUNT_PW=...
RA_SENDER_EMAIL=noreply@daasi.de
RA_DEFAULT_RECEIVER_EMAIL=noreply@example.com
RABBITMQ_URL=rabbitmq
RABBITMQ_USER=admin
RABBITMQ_PW=...
RABBITMQ_PORT=5672
... |
. For a list of general environment variables refer to didmos2 Provisioner.
After changing one or more values in the .env file a recompose has to be performed by using this command:
Codeblock |
---|
docker-compose up -d |
A simple restart of the affected containers does not suffice.
The basic principle of docker-compose and docker environment variables applies to all docker deployments for didmos 2.
ETL
Docker
didmos ETL consists of the following Docker container:
...
Configuration is possible via docker environment variables (for supported parameters) but generally via files in the volume. An example for the configuration using docker environment variables is described in section Provisioner - Docker.
Pwd Synchronizer
Todo?