ACTIVE DIRECTORY INTEGRATION

monarchtrophy

I am currently settingup osTicket for the first time, I was able to get it up and accesible, I installed the LDAP and AD extentionsion successfully but when I try to set the IP of the AD server it just times out and doesn't connect. Has anyone seen this before who might have a fix? Thank you

KevinTheJedi

monarchtrophy

Check your firewalls and all possible logs for any related errors.

Cheers.

monarchtrophy

Thank you for your response, I have been able to get everything up and running besides two things, agents are able to log in with their AD credentials but not users. I am also not able to send outgoing mail.

I changed the SMTP port to 587 in the ini and in the outgoing mail setting tied to the admin email but no luck, not sure what else it could be

KevinTheJedi

monarchtrophy

Make sure User authentication is enabled in the LDAP plugin settings. See if typing in the group/scope then username works (eg. users\username). If so you need to update your LDAP plugin settings to add Full DN for the search user and/or search base and retest.
You have not described your email setup nor what mail provider you are using so I'm not sure what could be going on or how to direct you.

Cheers.

monarchtrophy

This is how I have the configuration set up, typing the group\scope would not bind to the server, I am able to log in with my AD credentials as an agent but users can not, whether they are created in the admin panel and registered to AD or created automatically through ticket submission.

I was able to get the mailer issue figured out

KevinTheJedi

monarchtrophy

Here is a good checklist (created by a community member) of what each setting should contain:

https://forum.osticket.com/d/103605-ldap-authentication-lookup-not-working-with-tls-to-ad/5

In it, they explain that the Search User should typically be the correlating distinguishedName. Also, make sure your Search Base is indeed correct and contains the OU with all the Users/Agents.

If you've done all this and still can't get it to work then you will need to check your AD logs to see if an authentication attempt is even being made. If so, then you'll need to follow the pipeline down to see where exactly it's going wrong.

Cheers.