SGC for Tanium v1.8.2 on Australia: API Key Credential not being sent in REST step headers, 401error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello experts,
I am writing to report an issue I am experiencing with the Service Graph Connector for Tanium on my ServiceNow Australia dev instance.
Environment
- ServiceNow Version: Australia
- SGC for Tanium Version: v1.8.2 (Up to date)
Issue Description
After completing the Guided Setup with Token-based authentication, all API calls from ServiceNow to Tanium return a 401 Invalid Token error. This occurs both in the "Configure the View" step and during Scheduled Import execution.
Additionally, the "Test the Connection" step in the Guided Setup always remains in "Pending" status and never completes successfully, making it impossible to confirm whether the connection is established through the standard verification process.
Investigation Findings
Upon reviewing the Outbound HTTP Logs, we found that the Request headers are completely empty, the API Key Credential value is not being attached to the HTTP request headers.
We tested the Flow Actions "SG Tanium View" and "SG-Tanium Get Asset Rest Action" via Flow Designer Test. In the Execution Details for Step 2 (REST step), the Credential is correctly referenced (action > api_key > API Key), however the actual HTTP request is sent without any headers.
To confirm that the issue is on the ServiceNow side, we tested the same API Token directly via PowerShell against the Tanium API endpoint, and received a 200 OK response successfully. This confirms that the Tanium API Token and endpoint are both valid and functioning correctly.
Reference
A similar issue has been reported in the ServiceNow Community:
https://www.servicenow.com/community/developer-forum/flow-action-rest-step-issue-adding-credential/m...
Request
Could you please investigate the root cause of this issue and advise on a resolution or workaround?
Thank you for your assistance.
