Ad Widget

Collapse

LDAP authentication using CommuniGate LDAP

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Veselushko
    Junior Member
    • Nov 2015
    • 1

    #1

    LDAP authentication using CommuniGate LDAP

    Hello all. It`s my first post here, so i hope i will not make you mad with my noob questions

    I`m a total beginner with LDAP and getting serious trouble getting LDAP authentication work.

    We are using CommuniGate as LDAP server, so there are not so many tutorials how to get the work done.

    After multiple attempts the bind the server the zabbix successfully BIND to the server but the test connection with the test user is unsuccessful with error:

    ldap_bind(): Unable to bind to server: Invalid credentials [authentication.php:120 → CLdapAuthValidator->validate() → CLdap->checkPass() → ldap_bind() in /home/****/include/classes/ldap/CLdap.php:160]
    Login name or password is incorrect!


    The login user EXIST on LDAP and the password is CORRECT. If i change the user i get error LDAP USER NOT FOUND, which means that the test connection find the user if the user is the right one.

    I will be very thankful if you help me to enter the correct data. The most working config till now is:

    LDAP host - <IP of the LDAP server, without ldap:// and without port>
    Port - 389
    Base DN - cn=subdomain.domain.net
    Search attribute - uid
    Bind DN - [email protected]
    Bind password - password for the postmaster
    Login - postmaster (or any existing ldap user)
    User password - postmasters password (or any existing ldap user`s password)
  • dannyyang
    Junior Member
    • Aug 2016
    • 2

    #2
    I encountered the same problem

    I was also the first time using the LDAP ZABBIX certification, I encountered the same problem, how do you solve it ?

    Comment

    • kloczek
      Senior Member
      • Jun 2006
      • 1771

      #3
      Definition of the LDAP is about protocol.
      LDAP even stands for Lightweight Directory Access Protocol.
      As long as any new LDAP server application is compliant with few RFCs where LDAP a the pcommunication protocol is defined really doesn't matter what exact type of LDAP server application is working on LDAP server side interaction over LDAP will be exactly the same.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

      Comment

      • dannyyang
        Junior Member
        • Aug 2016
        • 2

        #4
        I got this sorted. It turned out I need @mydomain.com in the username. Thanks for the reply.

        [QLDAP even stands for Lightweight Directory Access Protocol.
        As long as any new LDAP server application is compliant with few RFCs where LDAP a the pcommunication protocol is defined really doesn't matter what exact type of LDAP server application is working on LDAP server side interaction over LDAP will be exactly the same.[/QUOTE]
        UOTE=kloczek;188442]Definition of the LDAP is about protocol.

        Comment

        Working...