<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Receiving a 401 Unauthorized error response from ServiceNow in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/688346#M3070</link>
    <description>&lt;P&gt;As a ServiceNow Admin, this is DEFINITELY a problem on the ServiceNow side.&amp;nbsp; Accounts calling the ServiceNow REST API need to be configured as web service only accounts, and have the correct roles applied based on what you're trying to read.&lt;/P&gt;</description>
    <pubDate>Wed, 22 May 2024 14:04:03 GMT</pubDate>
    <dc:creator>mjones1</dc:creator>
    <dc:date>2024-05-22T14:04:03Z</dc:date>
    <item>
      <title>Receiving a 401 Unauthorized error response from ServiceNow</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/679682#M2888</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Have anyone faced this issue where you received a Unauthorized 401 error response from ServiceNow?&lt;/P&gt;
&lt;P&gt;The scenario is as below.&lt;/P&gt;
&lt;P&gt;We are using a AD service account userA to interact with ServiceNow for incident creation .&lt;/P&gt;
&lt;P&gt;On Splunk Side, we are using Basic Auth.&lt;/P&gt;
&lt;P&gt;On AD, user account is set to never expired.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So far below we have checked the service account status. No changes was made but the issue was sudden.&lt;/P&gt;
&lt;P&gt;Ran the query&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;&amp;gt;index=_internal sourcetype="ta_snow_ticket host IN ( search head)&lt;/LI-CODE&gt;
&lt;P&gt;Above query was the one, we saw the Return code is 401 (Unauthorized)&lt;/P&gt;
&lt;P&gt;What else can be checked? As of now, we are planning to reset the service account password and try again.&lt;/P&gt;
&lt;P&gt;But if it works the issue is finding what cause the password to be changed when it have been set to never expires.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 17:45:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/679682#M2888</guid>
      <dc:creator>YJ</dc:creator>
      <dc:date>2024-03-26T17:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving a 401 Unauthorized error response from ServiceNow</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/682019#M2910</link>
      <description>&lt;P&gt;Have you verified that the used user has permissions to access ServiceNow via API? You could verify that with postman or a plain curl call.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 15:22:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/682019#M2910</guid>
      <dc:creator>PaulPanther</dc:creator>
      <dc:date>2024-03-26T15:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving a 401 Unauthorized error response from ServiceNow</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/682062#M2912</link>
      <description>&lt;P&gt;Hi Paul,&lt;BR /&gt;&lt;BR /&gt;That was what I was suspecting, the service account permission to access the Servicenow. The only problem i have is getting the other team(Servicenow) to provide info for my troubleshooting as they are denying that it is their end with issue. I was thinking since the service account is an AD account, there will surely be a security group assign to the service account . I have actually point out that the service account did not have any grouping assigned to it thus there could be a possibility that the servicenow account does not have the permission to access the Servicenow.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;There were actually similar issues where we found that some AD users security group were missing after an issue happened. I will try to go through this path and check on the permission again.. Thanks for the advice.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 23:44:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/682062#M2912</guid>
      <dc:creator>YJ</dc:creator>
      <dc:date>2024-03-26T23:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: Receiving a 401 Unauthorized error response from ServiceNow</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/688346#M3070</link>
      <description>&lt;P&gt;As a ServiceNow Admin, this is DEFINITELY a problem on the ServiceNow side.&amp;nbsp; Accounts calling the ServiceNow REST API need to be configured as web service only accounts, and have the correct roles applied based on what you're trying to read.&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2024 14:04:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Receiving-a-401-Unauthorized-error-response-from-ServiceNow/m-p/688346#M3070</guid>
      <dc:creator>mjones1</dc:creator>
      <dc:date>2024-05-22T14:04:03Z</dc:date>
    </item>
  </channel>
</rss>

