Jamf Error

[wildturkey07]

I recently installed the Jamf Service Graph Connector in our DEV environment. I have a new set of credentials that we created for this. They allow me to log into our Jamf instance. When I set up the service graph connector and run the "Test Load 20 Records", I receive the following error message: 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 57)

The credentials are correct and I have tried setting up the Service Graph Connector as Jamf Pro API and the Jamf Pro 10.35 or Higher option selected and I get the same error message on either one. Any idea of what I am doing incorrectly or has anyone came across this issue?

[AJ-TechTrek]

Hi @wildturkey07 ,

You must need to check the below.

1. Check the credentials once again 

2. Check the Mid Server connection to Jamf if you are using the Mid Server

3. Check the JAMF Connector is up to date on your Instance, if not you can update from ServiceNow Store.

4. Check the Service Mapping and Discovery pattern is up to date.

Also you can check the below docs.

https://developer.jamf.com/jamf-pro/docs/jamf-pro-api-overview

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1515911

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.

Thanks

AJ

Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/

[shivani42]

Hello @wildturkey07 ,

Did you get the solution for it. We are having the same issue.

Thanks,

Shivani

[wildturkey07]

Strangely enough we upgraded ServiceNow instances (from Tokyo to Vancouver) and it started working

[shivani42]

We have Washington version. I am getting the exact same error. I tried to see the request body and response. I got know we are not getting token.