<?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: What does this bug mean? in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355970#M8081</link>
    <description>&lt;P&gt;You're welcome. Hat tip goes to jkat54 for pinging me about this question.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jun 2017 22:04:54 GMT</pubDate>
    <dc:creator>nnmiller</dc:creator>
    <dc:date>2017-06-16T22:04:54Z</dc:date>
    <item>
      <title>What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355965#M8076</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Reading the known issues for upgrading to 6.5.3... and saw this:&lt;/P&gt;

&lt;P&gt;2013-08-19  SPL-73386   Users are not allowed to run historical scheduled search&lt;/P&gt;

&lt;P&gt;Workaround:&lt;BR /&gt;
1. Create a special power/admin user who can run scheduled searches.&lt;BR /&gt;
2. Assign this user ownership of the scheduled searches.&lt;BR /&gt;
3. Share the searches at the app level and grant read/write permission to the correct set of users. &lt;/P&gt;

&lt;P&gt;What does this mean exactly?  ALL users can't run historical searches?  Kind of a big bug, if that's the case... Is the solution saying that we need to create an additional admin/power user and then modify all searches?  &lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 12:58:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355965#M8076</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-06-16T12:58:18Z</dc:date>
    </item>
    <item>
      <title>Re: What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355966#M8077</link>
      <description>&lt;P&gt;I asked someone with access to Jira if they can elaborate on it for you.&lt;/P&gt;

&lt;P&gt;I've noticed you rarely accept answers though.  Can you please revisit some of your old posts such as this one?&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/405080/why-is-my-splunk-rest-api-search-not-working-and-g.html"&gt;https://answers.splunk.com/answers/405080/why-is-my-splunk-rest-api-search-not-working-and-g.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;And let some folks know if they've answered your questions by clicking on "accept answer" or responding to their answer.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 13:44:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355966#M8077</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-06-16T13:44:42Z</dc:date>
    </item>
    <item>
      <title>Re: What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355967#M8078</link>
      <description>&lt;P&gt;The bug is poorly worded. &lt;/P&gt;

&lt;P&gt;Basically, Splunk capabilities work exactly as intended. If a user does not have the capability to run schedule searches, even if an admin goes in and sets the restricted user's saved search to a scheduled search, the search won't run.&lt;/P&gt;

&lt;P&gt;A bug that allowed admin to successfully set a search as scheduled for a user without that capability was fixed. Another customer that was using that "loophole" filed this bug when the loophole stopped working.&lt;/P&gt;

&lt;P&gt;The work around to get the "loophole" back is by creating a the special "service account", giving ownership of the searches to that "service account", then giving each user that needs to modify those searches read/write permission.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 13:53:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355967#M8078</guid>
      <dc:creator>nnmiller</dc:creator>
      <dc:date>2017-06-16T13:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355968#M8079</link>
      <description>&lt;P&gt;Thanks. &lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 20:21:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355968#M8079</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-06-16T20:21:32Z</dc:date>
    </item>
    <item>
      <title>Re: What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355969#M8080</link>
      <description>&lt;P&gt;I wouldn't say rarely... as frequently as I should... probably not.  Some of that is because the answers don't work, or priorities change... nature of the job, I'm afraid.  I'll try to do better.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 20:22:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355969#M8080</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2017-06-16T20:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: What does this bug mean?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355970#M8081</link>
      <description>&lt;P&gt;You're welcome. Hat tip goes to jkat54 for pinging me about this question.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 22:04:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/What-does-this-bug-mean/m-p/355970#M8081</guid>
      <dc:creator>nnmiller</dc:creator>
      <dc:date>2017-06-16T22:04:54Z</dc:date>
    </item>
  </channel>
</rss>

