You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would lower the entry bar for using this container and make the world a kinder place.
In my case, I am trying to run this app and mock its LDAP service using this container. However, the app still complains that it can't find the LDAP service.
I am not sure if the issue is my configuration, the app or the LDAP container. By giving an example of what should work, I can conclude that there is nothing wrong with the LDAP container.
What is the feature you are proposing to solve the problem?
Adding a terminal command that verifies that the docker-compose service works as expected in the docker-compose section
Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.
Name and Version
bitnami/openldap:2.6.9
What is the problem this feature will solve?
It would lower the entry bar for using this container and make the world a kinder place.
In my case, I am trying to run this app and mock its LDAP service using this container. However, the app still complains that it can't find the LDAP service.
I am not sure if the issue is my configuration, the app or the LDAP container. By giving an example of what should work, I can conclude that there is nothing wrong with the LDAP container.
What is the feature you are proposing to solve the problem?
Adding a terminal command that verifies that the docker-compose service works as expected in the docker-compose section
GitHub Copilot suggested
But this did not work (
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
)I tried changing form
ldap://localhost:389
toldap://openldap:1389
to match what I think the example config does, but no success :(What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: