Ad Widget

Collapse

LDAP Setup Not Working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • monarch684
    Member
    • Oct 2017
    • 32

    #1

    LDAP Setup Not Working

    I am trying to setup LDAP for Authentication but cannot do so successfully. This is what I have for my settings:
    LDAP Host: ldap://xxx.xxx.xxx.xxx
    Port: 389
    Base DN: OU=Users-Network,DC=Company,DC=corp
    Search attribute: sAMAccountName
    Bind DN: CN=user,OU=Users,OU=Company,OU=Users-Network,DC=Company,DC=corp
    I have setup LDAP for other software and have had no issue. Any help would be appreciated.

    Server: Ubuntu Linux 16.04.3
    Zabbix Version: 3.0
  • long.chen
    Junior Member
    • Mar 2017
    • 14

    #2
    Try the Base DN without OU like the following:
    Base DN: DC=Company,DC=corp

    Comment

    • monarch684
      Member
      • Oct 2017
      • 32

      #3
      I am now getting:
      LDAP: Cannot bind by given Bind DN
      I tested using LDP and my credentials bind with no issue.

      Comment

      • long.chen
        Junior Member
        • Mar 2017
        • 14

        #4
        Your Bind DN path might be incorrect, please check you can search the user in active directory.

        Comment

        • monarch684
          Member
          • Oct 2017
          • 32

          #5
          Yes I can search the user in AD. I am using my username which has full domain admin privileges.

          Comment

          • long.chen
            Junior Member
            • Mar 2017
            • 14

            #6
            I don't see anything wrong here, a working example is like following:

            LDAP Host: xxx.xxx.xxx.xxx
            Port: 389
            Base DN: DC=Company,DC=corp
            Search attribute: sAMAccountName
            Bind DN: CN=user,OU=Users,OU=Company,OU=Users-Network,DC=Company,DC=corp
            Login: user
            User Password: xxxxxx

            Comment

            • monarch684
              Member
              • Oct 2017
              • 32

              #7
              Figured it out. This was technician error. I did not realize that the user password was the LDAP user password. I feel kinda stupid right about now.

              Comment

              Working...