Conf.json enquiry

[derekgreen]

Hi. I was hoping someone may be able to advise. We have been using Hornbill Service Desk for two months now, we are extremely happy with the service and would like to tie up some loose ends. When I run the conf.json executable to import new users from our Active Directory, we are only getting the basic information about the user - just their name. I need to reconfigure the conf.json to see if we can pull through more info, like job titles, email addresses and telephone numbers. I have attached snips of our current conf.json configuration and our standard AD user general info. Thanks!

conf.json.latest

[Martyn Houghton]

@derekgreen

When we were configuring our LDAP import I found it quite useful to use a LDAP tool to view the LDAP data and get the correct attribute names that were in use in our Active Directory, in order to populate the correctly the   "LDAPAttributes" section, as they have to be listed in their in order to use them in the field mapping.

The one I used was LDAPExplorerTool which is free - http://ldaptool.sourceforge.net/

Cheers

Martyn

[derekgreen]

Hi Martyn - thanks very much for the advice, but my manager here has a very strict 'no freeware' policy! Not always convenient but I understand his reasons.

[Martyn Houghton]

@derekgreen

That's, okay. the key thing is you will need to know the exact attribute names in LDAP source, in order to add them in the JSON. The link below might help you ascertain which attribute names you need.

https://msdn.microsoft.com/en-us/library/ms677980(v=vs.85).aspx

Cheers

Martyn

[Steve Giller]

Also, if you activate the Advanced View within AD Users & Computers you will expose additional tabs (assuming you have permissions) notably the Attribute Editor tab which lists every available attribute along with its current value - great for checking which are being used when there are multiple options for storing a particular piece of information.

[derekgreen]

Thanks to all, this has been so helpful. Definitely on the right track now.

[Ralf Peters]

@derekgreen

another option if you have access to run  powershell :

import-module activedirectory

get-aduser <account name> -properties *