<?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 Change forwarder password in a large deployment in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30311#M803</link>
    <description>&lt;P&gt;Hello, If I wanted to deploy out a large number of forwarders, what is the best practice to change the default splunkd password? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Anyone?!?! Anyone?!?!&lt;/P&gt;</description>
    <pubDate>Wed, 07 Dec 2011 18:06:38 GMT</pubDate>
    <dc:creator>DrewO</dc:creator>
    <dc:date>2011-12-07T18:06:38Z</dc:date>
    <item>
      <title>Change forwarder password in a large deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30311#M803</link>
      <description>&lt;P&gt;Hello, If I wanted to deploy out a large number of forwarders, what is the best practice to change the default splunkd password? &lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;

&lt;P&gt;Anyone?!?! Anyone?!?!&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2011 18:06:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30311#M803</guid>
      <dc:creator>DrewO</dc:creator>
      <dc:date>2011-12-07T18:06:38Z</dc:date>
    </item>
    <item>
      <title>Re: Change forwarder password in a large deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30312#M804</link>
      <description>&lt;P&gt;If you are talking about setting an initial password at installation time, I guess that you could add &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;path&amp;gt;/bin/splunk edit user admin -password &amp;lt;your new passswd&amp;gt; -auth admin:changeme
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;to your install/post-install script. However this depends on how you choose to deploy and on what platform. The bigger issue is how to change it at a later date. Unfortunately there is no safe way of doing it via the DeploymentServer. Neither can you upgrade the forwarder that way. &lt;/P&gt;

&lt;P&gt;Sorry,&lt;/P&gt;

&lt;P&gt;Kristian  &lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2012 17:13:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30312#M804</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2012-02-02T17:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: Change forwarder password in a large deployment</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30313#M805</link>
      <description>&lt;P&gt;You've probably solved your issue, but...&lt;/P&gt;

&lt;P&gt;I've deployed to a hundred or so Linux systems manually[1] via scripting.  &lt;STRONG&gt;On my UFs there is only one account, admin&lt;/STRONG&gt;, so I just copy the entire passwd file there.  &lt;/P&gt;

&lt;P&gt;Here's a few lines from my install script.  I've previously copied files to /tmp.  Running as the Splunk user (uid=1984), in $SPLUNK_HOME, any my &lt;EM&gt;semi-normal&lt;/EM&gt; user, these &lt;EM&gt;if&lt;/EM&gt; statements are run:&lt;BR /&gt;
&lt;PRE&gt;&lt;CODE&gt;# Splunk section&lt;BR /&gt;
if [ "$(id -u)" = "1984" ] ; then&lt;BR /&gt;
  tar zxvf /tmp/my-splunkuf.tgz&lt;BR /&gt;
  cp /tmp/passwd splunkforwarder/etc&lt;BR /&gt;
  chmod 600 splunkforwarder/etc/passwd&lt;BR /&gt;
  /opt/splunk/splunkforwarder/bin/splunk start --accept-license&lt;BR /&gt;
  exit 0&lt;BR /&gt;
fi&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;(Another comment, # is messing up the formatting) sudo-priv-user section&lt;BR /&gt;
if [ "$(id -u)" = "10101" ] ; then&lt;BR /&gt;
  sudo /opt/splunk/splunkforwarder/bin/splunk enable boot-start -user splunk&lt;BR /&gt;
  sudo chmod a+r /var/log/messages&lt;BR /&gt;
  sudo rm /tmp/passwd&lt;BR /&gt;
  rm /tmp/splunkme&lt;BR /&gt;
  rm /tmp/my-splunkuf.tgz&lt;BR /&gt;
  rm /tmp/adduser-splunk&lt;BR /&gt;
fi&lt;/P&gt;

&lt;P&gt;I have a custom tarball that I give to other groups for installation.  Among other things, it includes a custom outputs.conf pointing at my indexers and $SPLUNK_HOME/splunkforwarder/bin is included in the Splunk user's $PATH in .profile.  The other groups may have their own preferred password.  &lt;/P&gt;

&lt;P&gt;[1]"Manually" is misleading.  I run a few shell scripts that copy files to multiple systems targetted as UFs, log in and run those scripts, &lt;EM&gt;then clean up after themselves&lt;/EM&gt;.  SSH keys are enabled so I don't have to enter my password hundreds of times.&lt;BR /&gt;
If you understand this example, then you know what I mean.&lt;PRE&gt;&lt;CODE&gt;for i in $( cat new-UF-list ) ; do&lt;BR /&gt;
  scp adduser-splunk splunkme file1 file2 file3 ${i}/tmp&lt;BR /&gt;
  ssh $i /tmp/adduser-splunk&lt;BR /&gt;
  ssh splunk@${i} /tmp/splunkme&lt;BR /&gt;
  ssh $i /tmp/splunkme&lt;BR /&gt;
done&lt;/CODE&gt;&lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Nov 2012 20:58:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Change-forwarder-password-in-a-large-deployment/m-p/30313#M805</guid>
      <dc:creator>I_am_Jeff</dc:creator>
      <dc:date>2012-11-05T20:58:54Z</dc:date>
    </item>
  </channel>
</rss>

