LDAP authentication
You need to edit the file /home/devprom/docker/apache2/ldap.conf (or ldap.ssl.conf if you plan to use HTTPS) and specify the current parameters for connecting to your LDAP server - DN, password and so on.
Then, to enable this configuration, run the following commands:
docker exec -it alm-app bash
# a2dissite devprom
# a2ensite ldap
If you want to access the application over HTTPS, use a different configuration file, which also needs to be configured first:
docker exec -it alm-app bash
# a2dissite devprom
# a2ensite ldap.ssl
After switching the active Apache configuration, restart the container:
docker restart alm-app
By default, authentication uses the login based on the uid attribute in the LDAP directory. To implement email‑based authentication, edit the AuthLDAPURL parameter in the ldap.conf (or ldap.ssl.conf) configuration file:
AuthLDAPURL ldap://ldap.forumsys.com:389/dc=example,dc=com?mail,uid,cn,name??(objectClass=*)
Replace uid with mail (the attribute that stores the email address) between the question marks.
To enable automatic registration of domain users, in addition to the login attribute (either mail or uid), you must also provide three other attributes: cn, name, and dn.
LDAP/TLS or LDAPS
To improve the security of the connection to the LDAP directory, it’s better to use TLS or the LDAPS protocol—this way, the password isn’t transmitted in plain text over the network.
If you’re using self‑signed certificates, place the certificate on the server and add the following directives to the Apache configuration file (ldap.conf or ldap.ssl.conf):
LDAPConnectionTimeout 300
LDAPTrustedGlobalCert CA_BASE64 /var/www/devprom/engio_team.pem
LDAPTrustedMode TLS
LDAPVerifyServerCert off
Troubleshooting
If you encounter problems with authentication, edit the Apache web application configuration file (for example, /etc/apache2/sites-available/ldap.conf) and set a higher logging level:
LogLevel debug
Then restart the alm-app container or the apache2 service, log in again, and check the problem in the log file: /var/www/devprom/logs/error.log. The issue may be due to incorrectly specified LDAP connection parameters.