Jamf Connection Test Fails with 401 Unauthorized ErrorIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When we click on Test Connection on the Jamf connection record, it fails with a 401 Unauthorized error. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Update the system properties below to check the outbound HTTP logs: glide.outbound_http_log.override.level = all glide.outbound_http.content.max_limit = 1000 glide.outbound_http_log.override = true After doing that, test connection and navigate to the outbound HTTP log table: sys_outbound_http_log. Filter for the URL https://<JAMF endpoint>/api/v1/auth, you will see in the request that no token is being passed, which causes the request to fail with 401.However, if you check the outbound request to https://<JAMF endpoint>/api/oauth/token, you will see that a token is returned in the response. This token should be passed in the /api/v1/auth request. To resolve this, verify the following in Jamf: Go to Jamf Portal → Settings → API Roles and Clients → API Clients tab.Open the Client ID used in sgc-jamf.Edit it and check the Access Token Expiry Time. As per ServiceNow documentation, the token lifetime should be set to more than 3600 seconds (1 hour) to avoid potential issues. If it is set to 60 seconds, update it to the recommended value (3600) and then perform a Test Connection. This will resolve the issue. For reference:ServiceNow Documentation – Configure Jamf Integration:https://www.servicenow.com/docs/bundle/washingtondc-servicenow-platform/page/product/configuration-management/task/configure-jamf-integration.html#:~:text=If%20using%20Client,prevent%20potential%20issues.