[ZBXNEXT-4519] Cannot bind ldap server: authentication failed Created: 2018 Apr 24 Updated: 2023 May 11 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Appliance (L), Server (S) |
Affects Version/s: | 3.0.15 |
Fix Version/s: | None |
Type: | Change Request | Priority: | Major |
Reporter: | Zhou Zhenhua | Assignee: | Zabbix Support Team |
Resolution: | Unresolved | Votes: | 3 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
zabbix was installed on centos 6.8, needs to bind ldap server from Windows server 2008 R2 Enterprise |
Attachments: |
![]() ![]() |
Description |
Our zabbix component was installed on centos 6.8, we need to bind ldap information from Windows server 2008 R2 Enterprise. We could get user accounts from Windows server, but cannot bind ldap server in zabbix, it said unable to bind to server, invalid credentials, login name or password is incorrect. |
Comments |
Comment by Alexey Pustovalov [ 2018 May 10 ] |
do you use any special characters in login name or password? |
Comment by Andrew Twemlow [ 2018 May 29 ] |
Have you tried it without ldap:// for the LDAP host, we don't have that in our working configuration. |
Comment by Damian Ferrari [ 2019 Jun 13 ] |
I have same problem with Zabbix Server 4.2.3 and AD in Windows 2016. I've tried many times with all recommended parameters but no luck. Connection test from PHP script works. |
Comment by Dave Johnson [ 2022 Mar 09 ] |
At a small risk that I am missing something here, as I am really brand new to zabbix, so I apologize upfront if I stir the pot. Still, I reckon that this is probably the right thing to do as Microsoft has shifted to requiring using channel signing to attach to ldap now (using certificates). I felt the need to interject as I had to go through and generate some certs for linux machines (via sssd) and some apps (including postgres) to use ldaps and have the cert with private key authenticate into our AD. This is the method we use for querying AD when you are not joined in the domain. The certs need to be setup in AD to allow secure LDAP / AD access to the records in AD. Here are some additional notes on Microsoft getting people to migrate towards ldaps for years: In Aug 2019, Microsoft released "Microsoft Guidance for Enabling LDAP Channel Binding and LDAP Signing": That post includes the following link: Some documentation I refered to that helped me create the certs and perm them in AD: I saw this recent post, which may help too (I didn't use this, looks to be more for AD "auth use"): == Now with the above said, can Zabbix: a) authenticate against ldap with a certificate? (more universal and probably recommended) Again there is a small possibility I have this wrong as I am new to zabbix, but from what I read here and currently understand, zabbix "should" have a proper way of authenticating into AD using a cert, right? |