JAMF Connection Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2025 06:15 PM
I'm configuring Service Graph for JAMF , As part of the guided set up configure connection , I'm trying to test the connection . As i do that , I'm getting this 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2025 09:44 PM
Hi There,
The errors you mentioned means:
• No HTTP response was received at all (code -1 means connection failure, not a proper HTTP status like 401/403).
• It's likely a network, URL, or authentication issue, not just credentials.
You can Troubleshoot like below:
1. Verify API Base URL
• Go to your JAMF connection & credential alias in ServiceNow.
• Make sure the Base URL is in the correct format, e.g.:
https://your-company.jamfcloud.comOR
https://your-omprem-jamf-url:8443 • The URL should be accessible from ServiceNow MID Server, not your browser.
2. Check Credential Configuration
• Under the Connection & Credential alias, verify the basic auth or OAuth credentials:
â—¦ If using Basic Auth: check username/password (test directly in Postman or curl).
â—¦ If using OAuth 2.0, confirm:
• Token URL
• Client ID and secret
• Scope (if required)
3. Confirm MID Server Is Required & Working
• JAMF is usually an external API, so a MID Server is required unless you're on a network-allowed IP.
• Go to MID Servers > All MID Servers
◦ Ensure it’s validated, up, and has the correct capabilities (e.g., HTTP).
• Test connectivity from the MID Server to the JAMF API:
â—¦ Use MID Server > Script Include or ECC Queue to do a basic ping or REST call.
4. Test the API Manually (Outside SNOW)
• Use Postman or curl to test the exact API endpoint (e.g., /uapi/auth/tokens).
â—¦ If that fails too, the issue is with JAMF URL/credentials.
5. Check the System Logs in SNOW
• Go to System Logs > Errors or IntegrationHub Logs.
• Filter by source: JAMF, Service Graph, or the Flow you're using.
• Look for the raw error message, especially anything like:
â—¦ java.net.UnknownHostException
â—¦ javax.net.ssl.SSLHandshakeException
â—¦ 401 Unauthorized (if credentials are wrong)
6. Check for Proxy Issues (if behind firewall)
• If your organization uses a proxy for outbound calls, confirm if it’s needed for MID Server.
• You can configure proxy settings under MID Server properties.
NOTE: You can generate a test script to run from the MID server to confirm if it can reach JAMF. Please let me know if you need this
If my response helped please mark it correct and close the thread so that it benefits future readers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi MC30,
I'm facing the exact same issue.
But when I try using postman to hit below API I'm able to generate Bearer Token
https://yourserver.jamfcloud.com/api/v1/auth/token
I'm able to generate the token.
I even logged into the MID Server, and from there also while using postman I'm able to hit the API and generate the token.
But in ServiceNow I'm not able to generate the bearer token, I'm getting below error in ServiceNow
Error: The current operation ended in state: ERROR. Detail: Request not sent to uri= https://yourserver.jamfcloud.com/api/v1/auth/token : org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 *.jamfcloud.com,Detail: The current operation ended in state: ERROR. Detail: Request not sent to uri= https://yourserver.jamfcloud.com/api/v1/auth/token : org.apache.commons.httpclient.HttpException: The host did not accept the connection within timeout of 10000 *.jamfcloud.com
Can you please help on this, this is happening on Production.
Thanks for you help in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Hi MC30,
I'm facing the exact same issue.
But when I try using postman to hit below API I'm able to generate Bearer Token
https://yourserver.jamfcloud.com/api/v1/auth/token
I'm able to generate the token.
I even logged into the MID Server, and from there also while using postman I'm able to hit the API and generate the token.
But in ServiceNow I'm not able to generate the bearer token, I'm getting below error in ServiceNow
Error: The current operation ended in state: ERROR. Detail: Request not sent to URL = https://yourserver.jamfcloud.com/api/v1/auth/token : : The host did not accept the connection within timeout of 10000 *.jamfcloud.com, Detail: The current operation ended in state: ERROR. Detail: Request not sent to uri= https://yourserver.jamfcloud.com/api/v1/auth/token : : The host did not accept the connection within timeout of 10000 *.jamfcloud.com
Can you please help on this, this is happening on Production.
Thanks for you help in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Here Connection is not reaching to server because in that case server response code would be 3 digit like 200/401/403 etc.
It could be case of connection refuse and there could have multiple causes on this issue.
- Endpoint is not correct
- Mid server issue (make sure you have mentioned up and running mid server name in the integration configuration)
- Plugin is not up to date
- Scheduled Import Run As user should have cmdb_inst_admin role.
- page and pageSize is not been supported by the current DEV data stream OOB setup i.e., Computer Inventory
Please refer this links, see if it helps you:
Service Graph Connector for Jamf - Error: Unable t... - ServiceNow Community
Jamf integration (service graph connector) with se... - ServiceNow Community
