helm-openldap
helm-openldap copied to clipboard
Problems with Apache Ldap Studio (bug)
Right away, i do not think this is related to this chart in a direct way, since i can reproduce the issue with my docker-compose base boilerplate too (https://github.com/EugenMayer/docker-image-ldapexample/tree/main)
In both case, i can see that TLS/SSL is working (testing via network check in apache ldap studio). In the chart i leave the ports to how they are, in my boilerplate i map them to https://github.com/EugenMayer/docker-image-ldapexample/blob/main/docker-compose.yml#L17 (also tried to map them to 1389 / 1636 to see if the symmetry is an issue).
So in both cases, i fail to authenticate, because it creates a timeout on the check.
ldap1 | 671b7f53.2e5425a2 0x7fc27b9136c0 conn=1000 fd=14 ACCEPT from IP=172.31.0.1:36694 (IP=0.0.0.0:1636)
ldap1 | 671b7f53.310a8d76 0x7fc27b9136c0 conn=1000 fd=14 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.3 tls_cipher=TLS_AES_256_GCM_SHA384
ldap1 | 671b7f53.310cb67f 0x7fc27b9136c0 conn=1000 op=0 BIND dn="cn=admin,dc=kontextwork,dc=com" method=128
ldap1 | 671b7f53.310d95cf 0x7fc27b9136c0 conn=1000 op=0 RESULT tag=97 err=49 qtime=0.000007 etime=0.000111 text=
ldap1 | 671b7f58.2ee67601 0x7fc27b9136c0 conn=1000 fd=14 closed (connection lost)
Has anybody managed to get this running at all? I had no issues with osixia so i'am wondering. Tried. 2.5.18 too, same result. Tried to configure with
LDAP_ENABLE_PROXYPROTO: "yes"
LDAP_PROXYPROTO_PORT_NUMBER: 30389
LDAP_PROXYPROTO_LDAPS_PORT_NUMBER: 30636
but same timeout. I can connect without using TLS/SSL on those ports without any issues at the same time.
Thanks for any hint / sharing your experience