Unable to bind LDAP Server: Page 2

Unable to bind LDAP Server

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

KevinTheJedi

@Erudes

I want to clarify that the attribute names we are looking for are in the link I posted above and they are the values, not the keys. So for example in the link above for msad there is 'first' => 'givenName',. The attribute name we look for in AD is givenName.

Cheers.

Erudes

KevinTheJedi Oh ok,
So...if that's the case, then it doesn't work right

KevinTheJedi

@Erudes

Just tested and it works fine for me. It pulled my First + Last Name, my Email Address, and my Phone Number. I use default msad format and my attributes are named givenName, sn, mail, and telephoneNumber respectively. Note, it will only do this when it's creating the User in osTicket. If the User is already created in osTicket it will not sync/update the User's information.

What did you select as the LDAP Schema in the Plugin settings?

Cheers.

Erudes

KevinTheJedi
Ok users were already registered that's why it did not take it.
Now it works
Thanks everyone

« Previous Page