Facing an issue with JAMF Graph Connector - This is OOB Plugin

[Community Alums]

Hi Everyone, 

We have installed OOB Service Graph Connector for Jamf [2.12.2] plugin to pull computers data from Jamf into ServiceNow instance. After completing the setup, the job will load data into the import set. after some time, the connector will throw an error, causing the remaining import sets in the queue to stop processing and show as cancelled.
Error executing script: org.mozilla.javascript.JavaScriptException: Unable to connect to the JAMF API call. Please check your credential setup. Check the system log for further information. (sys_script_include.3fa7da3673b210104ae4b41afaf6a727.script, line 93).

above issue is happening occasionally.

When the job is completed without any error we observed other issues also..

All of the data imported into the import set is not transmitted to the target database; only a few entries will be updated in the target table, not all of them.
In ServiceNow, if the field already has a value, JAMF does not override it; if the value is empty then only JAMF updates the new value.[We observed the MAC address and assigned to fields. Because we are experiencing connectivity issues and data is not being sent entirely to the target table from the import set, we are unable to do thorough validation on this issue.

Kindly help on the above issues.

Thanks in advance,

Chaithanya

[Community Alums]

Hi @Community Alums 
Regarding  the issue where all of the data imported into the import set is not transmitted to the target database; we are observing the below error due to which it is going into the partial payload records.

errors": [],
"warnings": [
{
"error": "MISSING_MATCHING_ATTRIBUTES",
"message": "In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_network_adapter]. Add these input values in payload item

'{\"className\":\"cmdb_ci_network_adapter\",\"values\":{\"discovery_source\":\"SG-Jamf\",\"mac_address\":\"80:a9:97:0b:95:0d\",\"name\":\"80:a9:97:0b:95:0d\",\"last_discovered\":\"2024-07-12

23:04:18\"},\"internal_id\":\"87c24940ed634e54e03e5f145e2c6e4e\",\"sys_object_source_info\":{\"source_recency_timestamp\":\"2024-07-12

23:04:18\",\"source_feed\":\"SG-JAMF

Computers\",\"source_name\":\"SG-Jamf\",\"source_native_key\":\"ServiceNow_Jamf_HTTPS_Connection|ACE7B5CC-A0B1-55DF-8F6B-5D0FB0345377|80:A9:97:0B:95:0D\"},\"settings\":{\"updateWithoutDowngrade\":\"true\"},\"sys_ire_info\":{},\"display_values\":{}}'"

}
],
"operation": "INSERT_AS_PARTIAL",
"info": [],
"inputIndices": [
{
"mainIndex": 1,
"subIndex": 0
}
],
May I know what is causing this issue?

Regards,
Chaithanya

[SwathiPedireddy]

Hi @Community Alums 

Check Identification rule of network adapter and see all the attributes mentioned in identification rule are available in payload.

Thanks,

Swathi

[Narsing1]

If your JAMF Pro version is 10.35 or more, then only use the SGC for JAMF 2.12.2, otherwise need to go with 2.12.1.  Looks like the auth token has been changed in the new version which is not compatible to the users who uses JAMF Pro below 10.35

Thanks,

Narsing

[Community Alums]

Hi @Narsing1 

JAMF Pro version is  11.6.1 , I believe SGC JAMF 2.12.2 is compatible with that.

Thanks,

Chaithanya