Hey everyone. I've just successfully setup OSTicket version 1.12.3. I'm now trying to get AD authentication working for our techs only.

What I've done:

  1. I downloaded the auth-ldap.phar plugin file directly from https://osticket.com/download
  2. Placed the auth-ldap.phar file into my /var/www/html/osticket/include/plugins directory
  3. In 'Manage' --> 'Plugins' I adding our 'Default Domain' and the IP of our DNS server under 'DNS Servers'

Result:
When I click save I get the following message:
"Could not connect to MY.DOMAIN.WHATEVER.edu:389:389: Unable to bind to server OURSERVER.edu:389"

Background/Configuration Info:

  • We are running OSTicket on a CentOS 7 VM inhouse.
  • Running OSTicket version 1.12.3
  • PHP version 7.3.11
  • Apache version 2.4.6
  • Windows Server 2019

Any help would be appreciated.

  • RBGE replied to this.

    jlaroche Are you specifying the port number manually? If you're using port 389, just omit this part ( so ourserver.edu instead of ourserver.edu:389)

        As a side note: did you specify your search username and password? They also need to have permissions to browse AD.

          ntozier

          Yes. Within the "Connection Information" section I tried specifying a user that has the proper permissions. I always received the same error message: "Could not connect to MY.DOMAIN.WHATEVER.edu:389:389: Unable to bind to server OURSERVER.edu:389"

              Is the AD server running a firewall?
              Is the connection allowed from the webserver to AD?

              12 days later

              jlaroche I am just re-setting up a new instance of osTicket and I am literally JUST setting up my AD auth. A few questions and I am happy to help with this.

              1. do you have ANY 3rd party auth to your AD aside from workstations?
              2. What option did you tick for TLS?

                No, we don't have any 3rd party auth. I tried ticking the "Use TLS to communicate with the LDAP server". I also tried with that option unticked.

                  jlaroche
                  try using the IP address of the AD server to see if it's DNS related issue

                  Search Base: make sure it's correctly pointing to correct OU where your users are located. Like @ntozier said earlier
                  LDAP Schema: make sure it's selected correctly:

                    I got everything working. It turns out the issue was I needed to enter the "Search user:" in the format DOMAIN\username rather than just username like I had it before.

                    Tested and all is working well.

                    Thanks everyone.

                    ntozier changed the title to [resolved] Can't get LDAP plugin to work properly.
                    Write a Reply...