topic Re: How to change password using CLI in splunk in Installation

How to change password using CLI in splunk

vin02 — Sun, 07 Jun 2020 23:13:27 GMT

How to change password using CLI . We are using script(splunk edit user admin -password -role admin -auth admin:changeme ) to change the password.After the command password getting encryped but when we are trying again to login,again we are getting "changeme" as password?

Re: How to change password using CLI in splunk

somesoni2 — Mon, 03 Oct 2016 17:35:35 GMT

Are you specifying the password in the command?

splunk edit user admin -password newPassowrd  -auth admin:changeme

Re: How to change password using CLI in splunk

dslife_splunk — Sat, 29 Apr 2017 20:43:49 GMT

For the paranoid among us, you might want to follow this with either history -c to clear all your history or history -d <linenum> to delete the line with the password from your history file.

Re: How to change password using CLI in splunk

koshyk — Sat, 29 Apr 2017 21:28:42 GMT

or easier way is to put these lines into a script and call the script and delete the script afterwards
This way it won't show in history of commands.

Re: How to change password using CLI in splunk

adonio — Mon, 01 May 2017 02:05:57 GMT

not sure why @somesoni2 comment is not an answer...

 splunk edit user admin -password newPassowrd  -auth admin:changeme

Re: How to change password using CLI in splunk

bjoernhansen — Mon, 22 Jan 2018 16:51:15 GMT

The easiest way is actually to put a space in front of the command. That shouldn't log it to history.

Re: How to change password using CLI in splunk

highsplunker — Sun, 19 Apr 2020 17:30:18 GMT

hello. guys i don't understand. in order to change splunk admin pwd i need to know splunk admin pwd ? i don't get it...

Re: How to change password using CLI in splunk

rchudzinski — Tue, 01 Oct 2024 17:33:51 GMT

note: in my testing this behavor is specific to bash on linux.

Re: How to change password using CLI in splunk

cult_hero13 — Sat, 09 Aug 2025 13:16:56 GMT

Even then, the HISTCONTROL variable has to be set before running the command you don't want showing in history. Also, contrary to what I keep reading from Google results, this variable doesn't seem to be automatically set, or at least not on the various Linux distros I've used.