Unable to bind LDAP Server

KevinTheJedi

Try putting port 389 at the end of it. So instead of 10.8.10.40 put 10.8.10.40:389 and retry.

Cheers.

Erudes

KevinTheJedi
Thanks for replying
Still does not work
I don't think this is an OSTicket version problem, this should work anyway

KevinTheJedi

@Erudes

Looking at the error it’s saying that the credentials you configured is invalid. Please update the credentials to the correct ones and it should connect.

Cheers.

Erudes

KevinTheJedi
I was able to make it work, I had to fill out only the first part of it as it is an AD Domain.
After these changes will I be able to log in with any AD creds?
Do I have to configure HTTP Passtru?

KevinTheJedi

Erudes

As long as the username or email address they are using to login matches what’s in your AD.

The HTTP Passthru plugin is only if you want to configure the system to auto login users via credentials passed by the web server. Unfortunately we don’t have any documentation on this plugin but there are helpful posts on here and guides online.

Cheers.

Erudes

I can't seem to find an official tutorial on the forums for this...

Erudes

KevinTheJedi
Ok, good to be clear on what HTTP Passthru does.
The problem I'm facing now is that when I login with an AD user to the client portion of the portal it kinds of logs in but then I still see the "sign in" at the upper right hand side of the screen, so no actual authentication is done there (?).

I have the option for agents to register users only. Could that be a problem?

KevinTheJedi

@Erudes

In that case check your AD logs to see if an authentication attempt was made.

Cheers.

Erudes

KevinTheJedi I checked logs in EventViewer and they don't seem to be related to OSTicket
So hard to troubleshoot this...

I created a test AD User in the domain root and I get this now:

KevinTheJedi

Erudes

Use the email instead and see if that works.

Cheers.

KevinTheJedi

@Erudes

Wait, does that user exist in osticket yet? If not they need to be. Else you need to update your registration to Public.

Cheers.

Erudes

KevinTheJedi
KevinTheJedi
Yep, disabling that made it work. That is why I mentioned it in the previous comment.
I saw that email information and phone number is not captured despite that information being set in the object properties for the users.

KevinTheJedi

@Erudes

@ntozier is more familiar with the LDAP plugin and AD in general. When he’s online he can provide a little guidance here.

Cheers.

Erudes

KevinTheJedi

All right thanks, hopefully @ntozier can help me get those filled automatically hehe

ntozier

So I've read through this twice and I'm not real sure what it is you are trying to do, or what the problem is that you are experiencing is (it has been a long day so maybe my reading comprehension is bad right now).

The Authentication::LDAP and AD plugin lets users authenticate against an LDAP/AD server. But those users have to exist in osTicket to work right. We use a paid plugin to sync our users from AD to osTicket to make this easier.

Erudes

ntozier thanks for the reply

Well, users are not registered but they can login, (they get automatically registered after first login) create tickets, and even first and last name shows in their profile.
However, I cannot get other attributes to show up. Maybe thats why there's a paid plugin?

KevinTheJedi

Erudes

It should be pulling that info on User creation if it follows msad or RFC-2307 schemas. You can see this here:

https://github.com/osTicket/osTicket-plugins/blob/develop/auth-ldap/authentication.php#L21-L66

I would assume the attribute names in your AD don’t match what we are looking for (https://github.com/osTicket/osTicket-plugins/blob/develop/auth-ldap/authentication.php#L288-292).

Cheers.

Erudes

KevinTheJedi

I took a look at both but they both seem to display the same attributes, right?

KevinTheJedi

Erudes

That only shows the display names for the attributes not the actual attribute names. I’m not too familiar with AD so I have no idea where to find that unfortunately.

Cheers.

Erudes

KevinTheJedi Ok I get it,
so OSTicket looks for specific AttributeEditors, you're right, the default ones are named different in both scenarios.
I'm trying to create new attributes through Schema Editor, my AD account is already a member of enterprise admins and schema admin (I just added it), but the option "Create" is grayed out T_T