How to autofill user information using LDAP when creating new account.

silver310

I'm trying to autofill some additional fields like phone, worker id, table, etc.. based on information that is already present in Active directory.This way users won't have to input that information and it'll make like easier for us.How do i go about doing this? i've been reading around the forum and can't find any solution.Does the search base has anything to do with it? right now users can login using their AD credentials, but only emails get autofilled.

ntozier

Forum moderator @[deleted] has posted about this topic a few times. He also has a repo at github for his solution. I would recommend seaching and/or looking at: http://forum.osticket.com/d/discussion//ldap-fields-physicaldeliveryofficenamehttps://github.com/Chefkeks/osTicket-Addons

Chefkeks

@[deleted]0

Let me know if it works out for you and when you've questions, just post them here ;)

silver310

I'll check that out tomorrow, thanks.

silver310

Well, i tried using the addon, but after i enter all my info and hit save, i can't open the file again via web browser, i've tried like 10 times with different configurations, but everytime i hit save i can't open the file again.

silver310

Never mind, my password had a symbol in the beginning, noticed that in config.php it massed up the syntax.

silver310

OK i got it going, but i won't find any users from LDAP.i can see it printing "Found 1000 ldap entries!" so i assume it connected.But it doesn't find any users in ldap, even though i created those users using the LDAP addon from osticket.How is the script searching for users? on what attribute?I tried changing the search filter for the recommenden one for our AD server but that didn't help.

Chefkeks

It searches for users based on the SearchBase (under LDAP Settings).The ldap filter is hard-coded and makes sure only users with an enabled account and mail address are shown.Since it states "Found 1000 ldap entries" I think it connected well, so may suggestion: Make a new small testing OU with a few users and change the SearchBase to that specific OU, so it shows only e.g. "Found 5 ldap entries".Then take a look at the log (Debug = ON) if the ldap user can be matched (via login name / samaccountname) to the username of an user/agent in osTicket.I know the addon is definitely not perfect, but once configured it will work ;)Could be better and my goal is to make it into a plugin, but I'm "just" an administrator and not a developer, so lack of knowledge and time are the reason that it's not yet a plugin.PS: Could you post a screenshot once you got it working in that way that it says "Found 5 ldap entries" - so my suggestion with the small OU and a few users.

silver310

I can't do anything in active directory, it's a huge company and i only have read access so i can't test what you're proposing unfortunately.I've tried will a lot of search base, filters, domain controllers, but nothing works.I noticed in the osticket database there are "ost_user" and "ost_user_accout", ost_user holds the full name of the user, while ost_user_account holds the account name (samaccountname) wich is the same as in ldap, so i have no idea why it's failing.

Chefkeks

Hmm that's bad, but what does the log say?Usually it should list all ldap users (one by one) and tell whether an osTicket user/agent was found and synced or not.Below an example from our log file - you can see that the user admin is not found in ldap and sync was triggered for user "chefkeks" but the phone number was not updated since nothing changed since the last sync. In that way the shall be 1000 (since you said it stated "Found 1000 LDAP entries") entries in the log on your screen when you execute the addon. With that messages you could at least see if the ldap accounts were correctly found (successful ldap query) and if they could be merged with the osTicket agent/user accounts or not.From the log: Logging started...

------------------------------------------------------------------------------------------------

Found XXXXXX ldap entries!

Number of osTicket agents: XXXXXX

Modifiying now the following

osTicket agent: admin

osTicket Agent: admin not

existing in LDAP. Skipping this agent...

...

Number of osTicket users: XXXXXXX

minor-latin;mso-fareast-font-family;mso-fareast-theme-font-latin;

mso-hansi-theme-font-latin;mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font-bidi;mso-ansi-language;mso-fareast-language-US;

mso-bidi-language-SA"> Modifiying now the following

osTicket user: chefkeks

mso-ascii-theme-font-latin;mso-fareast-font-family;mso-fareast-theme-font:

minor-latin;mso-hansi-theme-font-latin;mso-bidi-font-family:"Times New Roman";

mso-bidi-theme-font-bidi;mso-ansi-language;mso-fareast-language-US;

mso-bidi-language-SA"> User information from LDAP:

'samaccountname'=chefkeks; 'cn'=XXXX ....

Number of changed database

entries for that user: 0 on phone