does not support 3 values in settings.conf (+ little other issue)

[ludolhoir]

Hello, hope you are well, still working on test environment, and things are going pretty well, except there is little issue when we try to add in the settings.conf more than two values in a raw,

example :

_snipeit_HDD_4 = hardware storage

works fine (only two values)

_snipeit_HDD_4 = hardware storage drive_capacity_mb
(or any as soon as we have three values)

and we have this error below. I tried with lot of subsets and everytime fails

File "/Users/ludoviclhoir/Desktop/jamf2snipe-main/jamf2snipe", line 901, in
jamf_value = jamf_value[item]
TypeError: list indices must be integers or slices, not str

another (very little one) is if we use the general mdm_capable_users result is {"mdm_capable_user":"username"} and should only be username, but it is not critical

thanks again alot for your precious help

[ludolhoir]

we did a test on our real/prod hosted one and everything runs smoothly except these little points, anyway nice

[ludolhoir]

just one thing with _snipeit_HDD_4 = hardware storage only we get all available values lie that

[{"disk":"disk0","model":"APPLE SSD AP0256N","revision":"1161.100","serial_number":"FV901430BHZLGY7C5","size":251000,"drive_capacity_mb":251000,"connection_type":"NO","smart_status":"Verified","partitions": etc etc , won't put it all here

[ParadoxGuitarist]

Just to throw out there:

another (very little one) is if we use the general mdm_capable_users result is {"mdm_capable_user":"username"} and should only be username, but it is not critical

This is actually a list of users. I get that you probably only have one person in the list (and most admins probably only have one user per device) , but Jamf doesn't care so it's putting in the whole "array". If you just need the user that's logged in, you could write an extension script to get the currently logged in user and write that to the JamfPro API then sync that data over.

I'm not sure there's a way to pick the "right user" out of the list and just sync that data since everyone else might use it differently.

[ludolhoir]

@ParadoxGuitarist thanks, if i may i have little other question, do you know if there is a way to get the personal recovery key, we faced an issue on jamf and lost a device (sill under investigation) and so lost his personal recovery key, and we would like to backup the keys somewhere, and i thought that with jamf2snipe which is great tool/script i could do it, but could not find anywhere how to, in api or whatever, it might not be possible, but asking in case you might help on this, if not we add it manually

[ParadoxGuitarist]

If the keys are enrolled in Jamf, they should be there, but they're not part of the regular API info. Essentially Jamf treats them like a password (because they are) so you'd have to make a special call, that gets logged and that your API user has to have a special permission for, to be able to do that. It's actually been a long time since I've used Snipe-IT but I don't know if they have a similar way to obfuscate custom fields for sensitive information (like Keys). That doesn't mean you can't do it, but you might potentially be making some security concessions depending on your setup @ludolhoir

[ghosden]

I'm facing the same issue when I try to pull the drive size using (_snipeit_drive_capacity_16 = hardware storage).

Ex:

[{"disk":"disk0","model":"APPLE SSD SM0512G","revision":"BXZ83A0Q","serial_number":"[Removed]","size":500277,"drive_capacity_mb":500277,"connection_type":"NO","smart_status":"Verified","partitions":[{"name":"Update","size":500067,"type":"other","partition_capacity_mb":500067,"percentage_full":1,"available_mb":350746,"filevault_status":"Not Encrypted","filevault_percent":0,"filevault2_status":"Not Encrypted","filevault2_percent":0},{"name":"Macintosh HD (Boot Partition)","size":500067,"type":"boot","partition_capacity_mb":500067,"percentage_full":5,"available_mb":350746,"filevault_status":"Not Encrypted","filevault_percent":0,"filevault2_status":"Not Encrypted","filevault2_percent":0,"boot_drive_available_mb":350746,"lvgUUID":null,"lvUUID":null,"pvUUID":null},{"name":"Preboot","size":500067,"type":"other","partition_capacity_mb":500067,"percentage_full":1,"available_mb":350746,"filevault_status":"Not Encrypted","filevault_percent":0,"filevault2_status":"Not Encrypted","filevault2_percent":0},{"name":"Data","size":500067,"type":"other","partition_capacity_mb":500067,"percentage_full":28,"available_mb":350746,"filevault_status":"Not Encrypted","filevault_percent":0,"filevault2_status":"Not Encrypted","filevault2_percent":0}]}]

How can I pull the subset "drive_capacity_mb" of the main drive ?

[ParadoxGuitarist]

@ghosden

The easiest way is to write a Jamf Attribute Extension Script to store that information then you can call and sync it directly without needing to parse the rest of the information.

The harder way to do it, would be to re-write the logic for parsing the settings config so the python can get that info. It'll take a lot of work of trying to figure out how to systemicly get down to that level, unless you wanted to shorthand an new setting that had custom parser just for drive capacity.

[michael-zukrow-da]

to confirm you are saying the documentation here is out of date? https://github.com/grokability/jamf2snipe/blob/main/settings.conf.example ?

GitHub

jamf2snipe/settings.conf.example at main · grokability/jamf2snipe

Import and sync assets from a JAMFPro instance to Snipe-IT asset management. - grokability/jamf2snipe

[LegendaryJackson]

Did anyone succeed with importing the drives capacity? I am struggling with this currently and there doesn't seem to be any other way than to somehow create an extension attribute first.

I'm thankful for any hint.

[ParadoxGuitarist]

@LegendaryJackson I think you've always been able to import the drive capacity, but the issue was that it wasn't very human readable since Jamf's API uses megabytes and not Gigs. The only way to get it easily human readable is to use Jamf's extension attributes afaik.

[LegendaryJackson]

@ParadoxGuitarist Alright. Then I probably have found a different issue. When I try to import the drives capacity with this syntax: _snipeit_HDD_4 = hardware storage drive_capacity_mb the field remains empty across all devices in snipe. When I try to get _snipeit_HDD_4 = hardware storage it gives back an error that I cant put an array into the filed in snipe.

I have created an extension attribute in Jamf now, so I could et at least some value in there, but I couldn't get it to work with the values from the example settings.conf.

[ParadoxGuitarist]

So the array error makes sense because there's mutliple keys/values in that object. If it's blank then you need to look at the raw data that Jamf is returning or open a ticket with them that that field is blank when it should be filled (or if it changed)

[stoneacher]

@LegendaryJackson Sorry to pop in here somewhat randomly but I'm also facing this issue with 3 keys.

How did adding an Extension Attribute solve the issue for you? We have multiple Extension Atrributes in our JAMF Pro instance for various reasons and adding another one will just add another field with the following syntax to the GET Response.

"extension_attributes":[
      {
         "id":<int>,
         "name":"<string>",
         "type":"String",
         "multi_value":<bool>,
         "value":"<String>"
      },
...

Am I missing something? If the name were to be HDD_Size I still won't be able to access the value with the settings.conf syntax of <snipe_key> = <jamf_key_lvl1> <jamf_key_lvl2>.

[LegendaryJackson]

@stoneacher
The initial issue we had was, that the HDD_size value is hidden in 3 layers of jamf_keys. You'd have to use a syntax of _snipeit_ssd = hardware storage drive_capacity_mb which is basically as if you were to go into a third level which the jamf2snipe script can't parse (<snipe_key> = <jamf_key_lvl1> <jamf_key_lvl2> <jamf_key_lvl3> where <jamf_key_lvl3> would be the capacity of the drive).

We finally caved in and just created an extension attribute that gets the value via this script:

#!/bin/bash
echo "<result>$(diskutil info /dev/disk0 | awk '/Disk Size/ { print $3 $4 }')</result>"

After that we just added this extension attribute to jamf2snipe's settings.conf and we got it into snipe-it.
(_snipeit_ssd_5 = extension_attributes 94 where "94" must be set to your particular extension attributes ID)