<?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: Splunk password issue in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640256#M16094</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;&amp;amp;&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/214410"&gt;@isoutamo&lt;/a&gt;&amp;nbsp; It has been fixed. I was used to save the seed file as user-seed.conf. So when I restarted the Splunk it saved as user-seed.conf.conf. So I corrected and saved the file only as user-seed and gives the results as user-seed.conf and generated the passwd &amp;nbsp;file also.&lt;/P&gt;</description>
    <pubDate>Mon, 17 Apr 2023 17:01:40 GMT</pubDate>
    <dc:creator>uagraw01</dc:creator>
    <dc:date>2023-04-17T17:01:40Z</dc:date>
    <item>
      <title>Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640232#M16087</link>
      <description>&lt;P&gt;I am getting below error. Although I have changed my password &amp;amp; user name from user-seed.conf. But still it is showing below error.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="uagraw01_0-1681743763165.png" style="width: 291px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24947iCBA2704B3A8CF68E/image-dimensions/291x112?v=v2" width="291" height="112" role="button" title="uagraw01_0-1681743763165.png" alt="uagraw01_0-1681743763165.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;But when I am login to UI, below are the error I am getting. Please help me how to fix this error.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="uagraw01_0-1681743624386.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24946iEABF0A1339D9872E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="uagraw01_0-1681743624386.png" alt="uagraw01_0-1681743624386.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 15:03:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640232#M16087</guid>
      <dc:creator>uagraw01</dc:creator>
      <dc:date>2023-04-17T15:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640239#M16088</link>
      <description>&lt;P&gt;Did you restart your splunk instance?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 15:17:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640239#M16088</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-04-17T15:17:43Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640240#M16089</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;Yes I have restarted&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 15:18:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640240#M16089</guid>
      <dc:creator>uagraw01</dc:creator>
      <dc:date>2023-04-17T15:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640241#M16090</link>
      <description>&lt;PRE&gt;# If the $SPLUNK_HOME/etc/passwd file is present,&lt;BR /&gt;the settings in this file (user-seed.conf) are not used&lt;/PRE&gt;</description>
      <pubDate>Mon, 17 Apr 2023 15:22:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640241#M16090</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-04-17T15:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640244#M16091</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;No passwd file is generating after restarting of the Splunk.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="uagraw01_0-1681745004108.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/24948i19CDA7704E054B59/image-size/medium?v=v2&amp;amp;px=400" role="button" title="uagraw01_0-1681745004108.png" alt="uagraw01_0-1681745004108.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 15:23:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640244#M16091</guid>
      <dc:creator>uagraw01</dc:creator>
      <dc:date>2023-04-17T15:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640249#M16092</link>
      <description>&lt;P&gt;To be fully honest, if you already have a working installation, I would just edit etc/passwd manually and insert a hashed password there.&lt;/P&gt;&lt;P&gt;But if you don't have etc/passwd and it's not getting created from user-seed.conf - there must be something wrong. Check the splunkd.log for errors. Permission issues?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 16:47:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640249#M16092</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-04-17T16:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640253#M16093</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;said you cannot have .../&amp;lt;SPLUNK_HOME&amp;gt;/etc/passwd file. If you have then you could use e.g.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.4/Security/Secureyouradminaccount#Create_admin_credentials_for_automated_installations_with_the_.27hash-passwd.27_CLI_command" target="_blank"&gt;Create admin credentials for automated installations with the 'hash-passwd' CLI command&lt;/A&gt;&lt;/P&gt;&lt;P&gt;to generate hashed password and add/change it into passwd file as already proposed.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 16:57:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640253#M16093</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2023-04-17T16:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640256#M16094</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;&amp;amp;&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/214410"&gt;@isoutamo&lt;/a&gt;&amp;nbsp; It has been fixed. I was used to save the seed file as user-seed.conf. So when I restarted the Splunk it saved as user-seed.conf.conf. So I corrected and saved the file only as user-seed and gives the results as user-seed.conf and generated the passwd &amp;nbsp;file also.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 17:01:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640256#M16094</guid>
      <dc:creator>uagraw01</dc:creator>
      <dc:date>2023-04-17T17:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk password issue</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640270#M16095</link>
      <description>&lt;P&gt;If no users exist that means that the $SPLUNK_HOME/etc/passwd file is missing.&amp;nbsp; To create a new admin user, you can use user-seed.conf and it is very easy.&amp;nbsp; &amp;nbsp;Just double check your steps here:&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Security/Secureyouradminaccount" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Security/Secureyouradminaccount&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 17 Apr 2023 18:01:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-password-issue/m-p/640270#M16095</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2023-04-17T18:01:53Z</dc:date>
    </item>
  </channel>
</rss>

