<?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: Search head pooling and authorize.conf in Security</title>
    <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83429#M2767</link>
    <description>&lt;P&gt;Maybe I should've searched better, but hopefully the link to the doc is useful to you. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 03 Apr 2013 15:41:33 GMT</pubDate>
    <dc:creator>echalex</dc:creator>
    <dc:date>2013-04-03T15:41:33Z</dc:date>
    <item>
      <title>Search head pooling and authorize.conf</title>
      <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83426#M2764</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm wondering how Splunk (4.3.x) deals with new roles created through the GUI. Since they're located in etc/system, I suppose you have to distribute any changes by yourself, or is there a way to automate this?&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2013 15:13:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83426#M2764</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2013-04-03T15:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: Search head pooling and authorize.conf</title>
      <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83427#M2765</link>
      <description>&lt;P&gt;I'm in a similar situation, but on 5.0.1. I'd love to see the solution as well.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2013 15:21:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83427#M2765</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2013-04-03T15:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: Search head pooling and authorize.conf</title>
      <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83428#M2766</link>
      <description>&lt;P&gt;Answering my own question, this situation has been documented. &lt;BR /&gt;
(&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.2/Deploy/Howauthorizationworksindistributedsearches"&gt;5.0.2&lt;/A&gt;, &lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.5/Deploy/Howauthorizationworksindistributedsearches"&gt;4.3.5&lt;/A&gt;)&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2013 15:39:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83428#M2766</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2013-04-03T15:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Search head pooling and authorize.conf</title>
      <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83429#M2767</link>
      <description>&lt;P&gt;Maybe I should've searched better, but hopefully the link to the doc is useful to you. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2013 15:41:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83429#M2767</guid>
      <dc:creator>echalex</dc:creator>
      <dc:date>2013-04-03T15:41:33Z</dc:date>
    </item>
    <item>
      <title>Re: Search head pooling and authorize.conf</title>
      <link>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83430#M2768</link>
      <description>&lt;P&gt;That is how we handle authorize.conf.  We have the common (shareable) information in a "splunk_system" app and the server specific information in $SPLUNK_HOME/etc/system/local.  We do this for all the $SPLUNK_HOME/etc/system/local config files.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2013 18:20:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Search-head-pooling-and-authorize-conf/m-p/83430#M2768</guid>
      <dc:creator>rmorlen</dc:creator>
      <dc:date>2013-04-03T18:20:25Z</dc:date>
    </item>
  </channel>
</rss>

