topic Re: Enabling 'Insecure Login' within web.conf in Splunk Search

Enabling 'Insecure Login' within web.conf

driva — Mon, 17 Aug 2020 13:23:06 GMT

Hi guys,

I'd like to be able to allow 'insecure' logins for my dashboards to be used with an internal signage solution.

I have changed the value of 'enable_insecure_login = False' to 'True' within var\run\splunk\merged\web.conf. I can save, close, then reopen the file and the value is still set as 'True'.

HOWEVER...

If I restart my Splunk server (to pick up the new change), the value reverts back to 'False' and I'm unable to access the dashboard using the insecure URL.

Does anyone know why the 'web.conf' file may reset the change I made after a restart?

Thanks for your help!

Best wishes,
D

Re: Enabling 'Insecure Login' within web.conf

impurush — Mon, 17 Aug 2020 19:31:42 GMT

HI @driva
If it is in a clustered environment, probably the artifacts are replicating when you restart the server and it replicated with the other servers.
You can try creating a web.con under /etc/system/local and add the insecure web login option and restart the server.

Re: Enabling 'Insecure Login' within web.conf

driva — Tue, 18 Aug 2020 07:13:48 GMT

Hi @impurush,

Thanks for getting back to me on this. It's not a clustered environment, just a standalone deployment which makes it an odd problem to have! I'll try and add the .conf file under /local and see if it works.

Thanks.

Best wishes,