topic Re: CLI "login failed" error on DS in Security

CLI "login failed" error on DS

cnuguri_ncc — Mon, 26 Jul 2021 08:13:03 GMT

Hello all,

Configured custom ssl certificates on Deployment Server (both splunkd and splunk web), and deployment clients are connecting to DS fine on this setup.

But, command line login started failing after this while running any commands on DS, Need help in resolving this please ? (we have requireClientCert=false).

Thanks in Advance
Chetu

Re: CLI "login failed" error on DS

codebuilder — Mon, 26 Jul 2021 21:28:51 GMT

It's asking for the Splunk admin account password that you would have created when installing Splunk. You can reset it via the web UI if you have access, or you can reset it with the user-seed.conf method.

https://community.splunk.com/t5/Security/How-to-Reset-the-Admin-password/m-p/10622

Re: CLI "login failed" error on DS

cnuguri_ncc — Tue, 27 Jul 2021 08:17:59 GMT

@codebuilder Sorry for not being clear enough, It fails when I enter the admin login details. The same username and password works with Splunk web though ( this is the admin account created at installation ).

And this started after I have setup SSL for splunkd port so wondering if that is affecting the CLI authentication ? Is there a way to setup cert authentication for CLI ?

Thanks
Chetu

Re: CLI "login failed" error on DS

codebuilder — Tue, 27 Jul 2021 13:50:17 GMT

Did you cycle Splunk after enabling web SSL? How are you running Splunk? As root, or another user?

Re: CLI "login failed" error on DS

cnuguri_ncc — Tue, 27 Jul 2021 15:51:54 GMT

Yes, restarted a few times.
Splunk is running as "Local System" on Windows.

Re: CLI "login failed" error on DS

codebuilder — Tue, 27 Jul 2021 17:32:47 GMT

What is the full command you are running? Also, have you looked at the the _audit index for any messages related to why the auth is not successful?

Re: CLI "login failed" error on DS

cnuguri_ncc — Fri, 06 Aug 2021 09:41:31 GMT

Thanks @codebuilder

Not exactly sure how, but it started working. I can only think the restart (although a few times) must have fixed this.