Service Graph Connector for Jamf Problem: Could not find path in stream

Miles Clark
Tera Contributor

We're attempting to incorporate Mac and iOS devices into the CMDB via the Service Graph Connector for Jamf.

We've walked through the Jamf SG setup, everything went fine until we tested the connection. When using the Pro API, we get the following error:

Error executing script : org.mozilla.javascript.JavaScriptException: java.lang.RuntimeException: com.glide.transform.transformer.exceptions.InvalidPathException: Could not find path in stream: $.results

If we use the classic api, the call succeeded.

We have ensured that the Base Path is clear in both instances.

Any idea what might be going on?

Thank you!

6 REPLIES 6

Open up flow designer and then open the hardwareinventory action.

Test the action using the connection alias that you configured.

From there please refer to the perviously posted link for helpful debugging help.

I would start with the HTTP response code.  That should give you a solid idea of where it is failing.  There may be a helpful response message as well.

The error indicates that the response is either not a 200 or has a response body that is different than an OOTB Jamf response.  A typical response would look like the following:

{
  "totalCount" : 50,
  "results" : [
    {
      "id" : "1",
      ...
    },
    {
      "id" : "2",
      ...
    },
    ...
  ]
}

Miles Clark
Tera Contributor

According to Now Support:

JAMF Pro API is not stable in our experience, so you will need to continue to use the classic API . Both the versions of query are working in our JAMF lab(SN Internal) environment.

Flow designer will not support below version of Jamf query:
/computers-inventory?section=GENERAL&section=APPLICATIONS&section=STORAGE&section=USER_AND_LOCATION&section=PRINTERS&section=HARDWARE&section=OPERATING_SYSTEM&page=0&page-size=100&sort=id%3Aasc`

For now customer are advised to use the Classic API version of Jamf.

We're going to stick with the classic api for the time being.  Thanks again for all the input.