-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Error message with button "Test LDAP" is empty #5540
Comments
LDAP configuration is detailed in detail here: https://snipe-it.readme.io/docs/ldap-sync-login |
Is this a windows AD or open source AD ? Based on your setting these would not be what I would use for windows AD. Let us know try help you further. |
Error message with button "Test LDAP" is empty snipe#5540
By the way, we use OpenLDAP on macOS (the one that came with Server.app). I've got my LDAP sync working already, so this one is for the person installing Snipe-IT after me :-) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
was already fixed. |
Please confirm you have done the following before posting your bug report:
Describe the bug
On the
/admin/ldap
-page, when pressing the button "Test LDAP", an error icon is shown without a text message.To Reproduce
Steps to reproduce the behavior:
/admin/ldap
ldap://myserver.mydomain.com
(I connect to an macOS Server.app Open Directory server)OpenDirReader
/admin/ldap
Expected behavior
A text message explaining the error (below the "Test LDAP" button, right of the red error-icon).
Screenshots
Server (please complete the following information):
Desktop (please complete the following information):
Error Messages
Description
Via Safari's developer console I see that the URL
/api/v1/settings/ldaptest
returns the JSON{"message": "Could not bind to LDAP: Invalid DN syntax"}
. This information is not shown to in the UI.Also: I figured out the exact problem why LDAP Test failed: the field "LDAP Bind Username" is put into the
bind_rdn
parameter of theldap_bind
function. Thebind_rdn
is not a username, but an LDAP dn format, likeuid=OpenDirReader,cn=users,dc=myserver,dc=mydomain,dc=com
.So this bug is about:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: