The Jamf Service Graph Connector and the process for updating a deprecated API call
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Regarding the Jamf SGC (and SGCs in general), it installs using /uapi/v1/computers-inventory in the data stream REST step, but that version has long been deprecated. In general with these SGCs, is it expected the ServiceNow will push an update to use the newer version of the API as part of updates for sn_jamf_integrate, or is it expected that we are supposed to separately test and update the version of these API calls installed as part of the SGC?
I did proactively create an idea about this (https://support.servicenow.com/ideas?id=view_idea&sysparm_idea_id=f6da68ce97323ad868d477121153afd9&s...) just in case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I just noticed that the SGC OOB API path is calling uapi/, not api/, which appears to be even more deprecated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
Yes, after doing search on Jamf , I came across these issue,
like silent failure :Jamf often returns partial payloads or empty fields without an error code resulting, ServiceNow receives a '200 OK' but the CMDB data is never actually updated.
and 500 Errors on Pagination 1000: Large environments cause the Jamf server to overwhelm and drop the connection mid-stream
Here is the KB article i 'm cross for jamf issue and it work around KB1962527
as I can not see your idea as getting message not authorized even try with partner account, i believe isn't it better to use classic api/custon api as avoid issue, please suggest
