Service Graph connector Jamf with ServiceNow OAuth error

SnehaSaran15
Tera Contributor

‎04-30-2025 05:05 AM

Hello

 

We are trying to setup a JAMF connection with ServiceNow using Service Graph Connector JAMF guided setup. We are using OAuth authentication which is working in Postman but in ServiceNow we are getting below error while clicking GET access Token

OAuth flow failed. Verify the configurations and try again. Error detail:invalid_scope

SnehaSaran15_0-1746014468879.png

 

While we are doing Test load 20 records from data source to test the connection then we are getting below error
Error- 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 401 (sys_script_include.3fa7da3673b210104ae4b41afaf6a727.script; line 57)

SnehaSaran15_1-1746014579339.png

 

 

  • 712 Views
4 REPLIES 4

Ravi Prakash Ro
Tera Expert

‎05-06-2025 05:14 AM

Hi Sneha,

I am also facing the same issue. Did you find any resolution for the same?

Please respond to this thread.

Thanks,

Ravi Roy

Venkatesh A K
Tera Contributor

‎06-03-2025 07:08 AM

Step 1: Update the Service Graph Connector

  • Always ensure that the Service Graph Connector for JAMF is updated to the latest version.
  • Many known issues are resolved in the newer releases—this should be your first step in troubleshooting.

Step 2: Review Outbound HTTP Logs

  • When you test with 20 records, the Outbound API calls are logged in the Outbound HTTP Logs table.
  • Check the logs for any errors using the link below:
     Outbound HTTP Logs – JAMF
  • Analyze the error messages to understand what went wrong (e.g., authentication failure, endpoint not reachable, etc.).

Step 3: Address JAMF Authentication Deprecation

  • JAMF has officially deprecated Basic Authentication for their Classic API.
  • Please refer to the JamF documentation for recent changes.

If you're currently using Username and Password credentials set up through JAMF's guided setup:

  • Uncheck the option “Use JAMF Pro API” in the ServiceNow configuration.
  • Save the changes.
  • Re-run the test.

    VenkateshAK_0-1748959653722.png

     

⚠️ Important: Do not make any other changes apart from unchecking the option.

0 Helpfuls

gustavo_and
Tera Contributor

‎06-11-2025 12:29 PM

Hi SnehaSaran15 ,

Did you find a solution to the problem? I am currently facing the same issues and the ServiceNow Documentation don't seem to mention any of this.

 

Thank you!

0 Helpfuls

Ravi Prakash Ro
Tera Expert

‎07-08-2025 02:56 AM

Hi All,

 

I found the solution for the above issue and thought of sharing here to help others, if anyone face similar issue.

Issue was with the OAuth scope value which was different than the one set in JAMF application. To check this follow the following path : Filter Navigator -> Application Registry -> JAMF OAuth Provider -> Related tab (OAuth Entity Scopes) ->  check the OAuth scope value (By default it will be "api-role:2") and ask JAMF admin to confirm if it is same at their end for the application created for this integration. Some time they allocate this value to other integration application. In that case we need to update the value in ServiceNow. 

Please mark helpful and correct answer or Let me know if you are still facing issue. I have deployed this integration successfully in production.

 

Thanks,

Ravi Roy