<?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 Search Head Deployer create .splunk folder in home directory in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/327994#M12281</link>
    <description>&lt;P&gt;When pushing a shcluster bundle as our sudo splunk user, I got the following message: &lt;/P&gt;

&lt;P&gt;Can't create directory "/home//.splunk": Permission denied&lt;/P&gt;

&lt;P&gt;I was able to mod the directory so it could create .splunk, but my question is why is it creating that in my home folder?&lt;BR /&gt;&lt;BR /&gt;
(I was not in my home folder when the push command was run and I was using the absolute path to the bundle push command)&lt;/P&gt;

&lt;P&gt;Thanks, all!&lt;/P&gt;</description>
    <pubDate>Tue, 06 Jun 2017 15:11:07 GMT</pubDate>
    <dc:creator>vicvaughan</dc:creator>
    <dc:date>2017-06-06T15:11:07Z</dc:date>
    <item>
      <title>Search Head Deployer create .splunk folder in home directory</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/327994#M12281</link>
      <description>&lt;P&gt;When pushing a shcluster bundle as our sudo splunk user, I got the following message: &lt;/P&gt;

&lt;P&gt;Can't create directory "/home//.splunk": Permission denied&lt;/P&gt;

&lt;P&gt;I was able to mod the directory so it could create .splunk, but my question is why is it creating that in my home folder?&lt;BR /&gt;&lt;BR /&gt;
(I was not in my home folder when the push command was run and I was using the absolute path to the bundle push command)&lt;/P&gt;

&lt;P&gt;Thanks, all!&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 15:11:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/327994#M12281</guid>
      <dc:creator>vicvaughan</dc:creator>
      <dc:date>2017-06-06T15:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Deployer create .splunk folder in home directory</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/327995#M12282</link>
      <description>&lt;P&gt;When you run a Splunk command that requires authentication, Splunk creates an auth token in ~/.splunk on whichever user you ran the command on. The token contains a username and session key that Splunk uses to re-authenticate itself in case you need to run additional CLI commands. This is usually not a problem if you run Splunk CLI commands from the same user that Splunk runs as.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 18:41:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/327995#M12282</guid>
      <dc:creator>masonmorales</dc:creator>
      <dc:date>2017-06-06T18:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Search Head Deployer create .splunk folder in home directory</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/656808#M27417</link>
      <description>&lt;P&gt;Are there any security related concerns due to this , as this file contains the authToken ? Can this be miss used&amp;nbsp; in any possible way?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Sep 2023 11:21:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Search-Head-Deployer-create-splunk-folder-in-home-directory/m-p/656808#M27417</guid>
      <dc:creator>jaihingorani</dc:creator>
      <dc:date>2023-09-06T11:21:43Z</dc:date>
    </item>
  </channel>
</rss>

