Splunk Search

Enabling 'Insecure Login' within web.conf

Path Finder

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'.


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,

Labels (1)
0 Karma


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.

Tags (1)
0 Karma

Path Finder

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.


Best wishes,


0 Karma
Get Updates on the Splunk Community!

Splunk Forwarders and Forced Time Based Load Balancing

Splunk customers use universal forwarders to collect and send data to Splunk. A universal forwarder can send ...

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...