JAMF adapter username import

[Richard Jenkins]

I am trying out the JAMF adapter for Assets Data Manager (ADM) and noticed that there is no username field being pulled. None of the fields are for usernames, so which field is everyone using to get the username assigned the JAMF device? If not any, how is anyone syncing the name to a device?

I first though that the NAME field is used, but I was told by our JAMF admin that this field is for device name. Any advice or ideas are appreciated.

[Hun Chan · Accepted solution]

Hi Richard, Thorben,

Below is the process in which the JAMF adapter operates:

1. The adapter client directly calls the API to retrieve a list of computer IDs.

   1. API: {api-url}/JSSResource/computers

   2. Method: GET

   3. Response: A list of computer IDs.

2. It then uses the computer IDs to call the API and retrieve computers information.

   1. API: {api-url}/JSSResource/computers/id/{id}

   2. Method: GET

   3. Attributes retrieved include: Name, MacAddress, IpAddress, SerialNumber, Platform, AssetTag, ReportDate, LastContactTme, Make, Model, OsName, OsVersion, ServicePack, ProcessorType, ProcessorArchitecture, ProcessorSpeed, NumberProcessors, NumberCores, TotalRam, IsLeased, PoNumber, Vendor, WarrantyExpires, LeaseExpires

You are correct, NAME refers to DeviceName or HostName. Username is not one of the fields listed above because the information obtained relates to computer (hardware) based information that describes the hardware. Having said that, we can look at potentially adding this field into the API call if at possible.

[Richard Jenkins]

Thank you for the quick response. I was actually trying the /JSSResource/computers/serialnumber/{serial_number} api call but I do not have the necessary permissions to run it. I am currently working with our JAMF admin for permissions in order to run it.

Having the username imported for the device is extremely helpful as we can directly tie in devices of the user in assets when importing. Otherwise, I would have to externally call the api to get the info and then run it as an Automation for Jira rule.

Thank you as well for the outstanding effort on this application. It is looking wonderful!!

[Hun Chan]

Hi Richard, Thorben,

This JAC ticket (https://jira.atlassian.com/browse/JSDCLOUD-15427) is an example of the request to be able to customize the attributes returned for the JamF adapter in response to your request.

Also, there is this JAC ticket that my colleague Karyn mentioned earlier: (https://jira.atlassian.com/browse/JSDCLOUD-15355) This is an example of the request to be able to customize the attributes returned for all adapters (not just JamF).  We suggest voting for these (& watching) as this will assist with getting this higher in our Roadmap priorities.  We will also update JAC tickets when we have a timeline for a change, hence the suggestion to watch it.

Regards,

Hun

[Richard Jenkins]

Absolutely! Voting on it now!

[Thorben Petersen]

Great question. In addition I’d like to know how Atlassian plans to expand the attributes / objects generally. 

[Karyn Findlay]

Hi @Thorben Petersen ,

We're seeing lots of requests to modify adapters and we are using JAC tickets to focus our energy on those that our customers want to see.  This JAC ticket (https://jira.atlassian.com/browse/JSDCLOUD-15355) is an example of the request to be able to customize the attributes returned for all adapters (not just JamF).  I'd suggest voting for this (& watching) as this will assist with getting this higher in our Roadmap priorities.  We will also update JAC tickets when we have a timeline for a change, hence the suggestion to watch it.

Regards,
Karyn