<?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: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/581941#M102551</link>
    <description>&lt;P&gt;If anyone is coming across this in 2022, you should know that there's a pretty easy workaround for this nowadays. The issue is with XML parsing, but Splunk allows you to output the results in JSON format with a simple change to your rest query. Instead of my query for lookup transforms:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest /servicesNS/nobody/app/data/transforms/lookups  splunk_server=local&lt;/LI-CODE&gt;&lt;P&gt;You just add the&amp;nbsp;&lt;STRONG&gt;output_mode=json&lt;/STRONG&gt; GET argument to it, like so:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest /servicesNS/nobody/app/data/transforms/lookups output_mode=json splunk_server=local&lt;/LI-CODE&gt;&lt;P&gt;This resolved this issue for me immediately.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jan 2022 02:07:46 GMT</pubDate>
    <dc:creator>haraksin</dc:creator>
    <dc:date>2022-01-21T02:07:46Z</dc:date>
    <item>
      <title>Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315758#M59086</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I use this query almost every day :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| rest /services/authentication/users
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But today it doesn't work, I get this error message :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Failed to parse XML Body:&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt; &amp;lt;!--This is to override b...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And I don't have the end of this message.&lt;/P&gt;

&lt;P&gt;Other rest commands work fine.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Oct 2017 16:35:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315758#M59086</guid>
      <dc:creator>JuGuSm</dc:creator>
      <dc:date>2017-10-17T16:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315759#M59087</link>
      <description>&lt;P&gt;Same problem for me with&lt;BR /&gt;
    | REST /services/data/lookup-table-files&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; | rest /services/authentication/users
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;works for me.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jan 2018 14:22:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315759#M59087</guid>
      <dc:creator>mbrettschneider</dc:creator>
      <dc:date>2018-01-11T14:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315760#M59088</link>
      <description>&lt;P&gt;I just had a case with the exact error. It turned out to be related to Splunk's inability to process the data due to some issue in the data.&lt;/P&gt;

&lt;P&gt;In the case I worked on, there were base64 VALUES that had a hidden character at the beginning. &lt;/P&gt;

&lt;P&gt;I am aware of one other case, which had unusual (not UTF-8) characters in the data.&lt;/P&gt;

&lt;P&gt;Solution:&lt;BR /&gt;
Fix your data. Examine it with a programming Tool (I use MacVIM, and GVIM). You may not see the problem when just looking at the logs.&lt;/P&gt;

&lt;P&gt;If you can't fix your data prior to ingestion, what you can do is go into the search.log, determine which search (or source) is generating the problem and disable it. I realize this is a temporary solution, but it is a workaround until you can clean up your data.&lt;/P&gt;

&lt;P&gt;I was not able to find any "Splunk Bugs"  on this particular issue, possibly because it falls more under "quality of incoming data".&lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2018 19:27:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315760#M59088</guid>
      <dc:creator>scorrie_splunk</dc:creator>
      <dc:date>2018-03-13T19:27:35Z</dc:date>
    </item>
    <item>
      <title>Re: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315761#M59089</link>
      <description>&lt;P&gt;My problem has been resolved a few months ago and it was exactly what you described.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Mar 2018 05:31:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315761#M59089</guid>
      <dc:creator>JuGuSm</dc:creator>
      <dc:date>2018-03-14T05:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315762#M59090</link>
      <description>&lt;P&gt;Hey guys,&lt;/P&gt;

&lt;P&gt;how have you been able to fix this?&lt;/P&gt;

&lt;P&gt;I have the same issue with&lt;BR /&gt;
| rest splunk_server=local /services/search/jobs&lt;/P&gt;

&lt;P&gt;Can't find a safe way to find the malicious characters, although splunk is stating its this:&lt;BR /&gt;
Entity: line 305799: parser: Input is not proper UTF-8, indicate encoding !\nBytes: 0xC3 0x20 0x2E 0x2E&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 21:40:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/315762#M59090</guid>
      <dc:creator>effem</dc:creator>
      <dc:date>2019-11-25T21:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: Why doesn't my REST query to /services/authentication/users work anymore all of a sudden?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/581941#M102551</link>
      <description>&lt;P&gt;If anyone is coming across this in 2022, you should know that there's a pretty easy workaround for this nowadays. The issue is with XML parsing, but Splunk allows you to output the results in JSON format with a simple change to your rest query. Instead of my query for lookup transforms:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest /servicesNS/nobody/app/data/transforms/lookups  splunk_server=local&lt;/LI-CODE&gt;&lt;P&gt;You just add the&amp;nbsp;&lt;STRONG&gt;output_mode=json&lt;/STRONG&gt; GET argument to it, like so:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest /servicesNS/nobody/app/data/transforms/lookups output_mode=json splunk_server=local&lt;/LI-CODE&gt;&lt;P&gt;This resolved this issue for me immediately.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jan 2022 02:07:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-doesn-t-my-REST-query-to-services-authentication-users-work/m-p/581941#M102551</guid>
      <dc:creator>haraksin</dc:creator>
      <dc:date>2022-01-21T02:07:46Z</dc:date>
    </item>
  </channel>
</rss>

