Recieve error message when setting up Service Graph Connector for jamf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 12:13 PM
When configuring the Service Graph Connector for jamf we receive the following error message when trying to connect to the jamf application.
"org.mozilla.javascript.JavaScriptException: Error: Unable to make a connection to JAMF API call. Please check your credential configuration. Check system log for more details. HTTP return status code was -1 (sys_script_include.3fa7da3673b210104ae4b41afaf6a727.script; line 93)"
We are using a local user account and have confirmed it has the privileges it needs to load the data, any guidance on how to remediate this error would be much appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2024 07:07 AM - edited 03-11-2024 07:27 AM
Both computers and Mobile devices have stopped working. Same error (line 93 & 198) in the script include: JAMFDataSourceUtil.
I also updated the plugin to the latest version. previous (originally working : 2.11.0, new version: 2.12.1
Tested the credentials and JAMF endpoint using Postman.
I can get the records without any problem.
In flow designer I can see the computer action that is used by Service Graph Connector for Jamf . This action uses /computers/subset/basic as endpoint. When trying this in Postman the first time it fails, second time it returns the expected results
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2024 04:54 AM
can you share the script present on line 93 & 198 from the script include: JAMFDataSourceUtil.
Regards,Sushant Malsure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2024 05:09 AM
these lines are the 'catch' commands.
To solve it, I had to change the JAMF setup to JAMF PRO API and then it worked again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2024 05:11 AM
I had to change the JAMF setup to use Jamf API PRO and API version above ...
Then it worked again.