Skip to content
English
  • There are no suggestions because the search field is empty.

LDAPS from version 4.6.x not accessible

LDAPS requires CA certificates, if these are not found when logging into the toolbox, a login is not possible despite otherwise correct configuration.

The storage location of the certificates may vary depending on the operating system. If your operating system is not listed here, please search for the corresponding storage location yourself.

Provide LDAPS certificate of the LDAP library

To do this, the .env file in the main directory of the toolbox must be adapted. Add the following line to the file:
LDAPTLS_CACERT=/etc/ssl/certs/ca-certificates.crt

The file must then be saved, and the containers restarted for the changes to take effect. Login with LDAPS should then be possible again.

Use all certificates of the host system

If you want to use all certificates of the host system, you must adapt the docker-compose.yml file in the main directory of the toolbox. In the file, navigate to the line server: and then to the subsection volumes: Here you will already find at least three entries:

- './store/toolbox/config:/store'
- './store/toolbox/uploads:/app/web/uploads'
- './store/toolbox/logs:/app/var/logs'

These entries represent a connection from the file system of the host system to the file system of the server container. This makes it possible to directly access files from within the container on the host system.
The three existing entries must not be removed. These serve the following purpose:

  • ./store/toolbox/config Configuration parameters and license information
  • ./store/toolbox/uploads files uploaded by users
  • ./store/toolbox/logs various log files

These three volume entries are now extended by a fourth entry so that the CA certificates can be accessed.

If you are using RedHat:

- '/etc/pki/tls/certs/ca-bundle.crt:/etc/ssl/certs/ca-certificates.crt'

If you are using Debian:

- '/etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt'

The file must then be saved, and the containers restarted for the changes to take effect. Login with LDAPS should then be possible again.