-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No access to LDAP directory #1041
Comments
Please don't open an issue for a question. You should use the mailing list for that (https://ltb-project.org/contact.html), or open a discussion (https://github.com/ltb-project/self-service-password/discussions). You can give a look at the error_log configured in your webserver to understand what's wrong with your configuration. |
Thanks for the quick reply!
Please forgive me for this.
Do you mean it should be like this?: config.inc.php
ldap.conf
the last from my log
|
I believe it should be |
Thanks for your reply. I think not, the documentation specifies port 389 (Lightweight Directory Access Protocol). Anyway, I get the error:
I think there is a mistake in the TLS configuration. Or the problem is in the domain controller. |
ah, well - don't you need a valid certificate for TLS? Can you use hostnames instead of IP addresses? for me a successfull connection looks like (note: 192.168.10.10 is the IP of the ldapserver.domain.de)
the domain related settings look like this for me:
good luck! PS: if you come around the error |
Have a nice day everyone.
Until recently I worked only with MS Windows and all this is new to me. Please do not swear.
I have Debian 12 and installed SSP version 1.7.2 on it. When I try to change the password I get a message in the web interface "No access to LDAP directory". Auditing seems to be enabled, but the log file is empty. Where should I start solving the problem? I will be grateful for any help. My config file is below. I apologize for some experiments in it, they are commented out.
I apologize if I did something wrong.
Thank you.
The text was updated successfully, but these errors were encountered: