TLS: can't accept: No certificate was found.. #105
Comments
I have the same problem |
we also have this problem. while playing around with
i noticed that it was not working from outside the container. there i got the following log lines:
But from inside the openldap containter it seems to work:
so how can this be solved? is this typical for a problem with the network configuration? or a dns reverse lookup problem? how can i test this? |
I ran into the same issue and found a solution. The problem arises from client verification and can be fixed by adding |
@betagan thanks for the response indeed LDAP_TLS_VERIFY_CLIENT is set to Possible values are : never | allow | try | demand It's not really a good idea to use the image default certificate and certificate authority. |
I have this same issue. The suggested solution of: --env LDAP_TLS_VERIFY_CLIENT=try Not sure why it's not verifying the client certificate. Any reason for this? |
Hi All,
i'm try to connect via jxeplorer to the docker container where ldapd is running in.
Information which i use to connect to ldap via jxplorer:
Everytime a connection is successfully i face the dialog regarding the not trusted certificate. I can also show the certificat and see at the Subject this: CN=docker-light-baseimage So there should be a certificate exist.
But if i klick on "trust for this session" i face following error at the docker container:
of course without ssl its works well. But its not my intension to work without ssl.
If i check in the container how about certificates i found this:
i have no idea why its not found any certificate.
I have attach the output if i start the server by running following command:
docker run -it --name ldap -p 389:389 -p 636:636 osixia/openldap:1.1.7
ldap_start.txt
I have no idea how to fix it.
Maybe some of you will help to fix the issue?
greeting,
Cinux90
The text was updated successfully, but these errors were encountered: