Splunk Search

Enabling 'Insecure Login' within web.conf

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

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

0 Karma

impurush
Contributor

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

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

Thanks. 

Best wishes,

D

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...