SSL and HTTPS
To enable HTTPS access, you need to copy your key and certificate into the alm-app container at the following paths: /etc/ssl/private/alm-selfsigned.key and /etc/ssl/certs/alm-selfsigned.crt, respectively. Alternatively, you can use a self‑signed certificate; to install it, run the following commands:
docker exec -it alm-app bash
# openssl req -x509 -nodes -days 365 -subj "/C=CA/ST=QC/O=Engio/CN=engio.team" -newkey rsa:2048 -keyout /etc/ssl/private/alm-selfsigned.key -out /etc/ssl/certs/alm-selfsigned.crt
After that, you need to activate the Apache configuration that is set up to use HTTPS:
docker exec -it alm-app bash
# a2dissite devprom
# a2ensite devprom.ssl
If you are using a configuration with LDAP connectivity, use a different configuration file instead:
docker exec -it alm-app bash
# a2ensite ldap.ssl
Once the alm-app container is restarted, the application will be accessible via HTTPS.
Application configuration
To ensure the application generates correct links for accessing project artifacts, you need to inform it that HTTPS is being used.
To do this, go to the administrative section, then to the menu: Settings → Application. On the form, enter 443 in the “Connection port” field and save the settings.