Is this a new feature request?

• I have searched the existing issues

Wanted change

The usage of LDAPS requires the requesting client to trust the Issuing CA of the Domain controller Certificate or the Self Signed Certificate of the Domain controller. (If you dont have a CA Windows generates its own Cert for the Domain Controller)
Currently there is no way for the container to trust the Domain controller and when setting up LDAPS it throws a generic "Can not connect" error.

Reason for change

To make it easier to use LDAPS out of the box which the software has support for.

Proposed code change

My current workaround is having this script mounted with the cert and it running on start.

    volumes:
      - /opt/projectsend/config:/config
      - /opt/projectsend/data:/data
      - /usr/local/share/ca-certificates/RootCA1_base64.crt:/usr/local/share/ca-certificates/RootCA1_base64.crt:ro
      - /opt/projectsend/compose/ca-setup.sh:/etc/cont-init.d/99-ca-setup:ro

#!/bin/sh

set -e
echo "[ca-setup] Starting CA Setup."

apk add --no-cache ca-certificates
cat /usr/local/share/ca-certificates/RootCA1_base64.crt >> /etc/ssl/cert.pem
update-ca-certificates

echo "[ca-setup] Setup completed."