Security

Using custom SSL Certificates with the Management Port causes splunkweb and the management port to be unresponsive

brandonmosherx
New Member

Splunk 6.4.1

Ways I've approached this and it hasn't been successful:

  • Using the same certificate as the SplunkWeb SSL certificate (splunkweb works on it's own with the SSL certificate being successful.)
  • Using a different certificate than the SplunkWeb SSL certificate (without a password)
  • Using a different certificate with a password, and configuring the server.conf to utilise that password

The moment that I configure the server.conf to not utilise the certificates I've created, splunkweb goes back to normal after I restart. And I can access the management port as well (even though the default certificates are invalid in the first place.)

Any ideas on what the problem might be, or if it's related to the current Splunk version?

Thanks!

0 Karma

yongchien
New Member

Hi I'm having the same problem as well, anyone here care to shed some lights? Thanks

0 Karma
Get Updates on the Splunk Community!

What the End of Support for Splunk Add-on Builder Means for You

Hello Splunk Community! We want to share an important update regarding the future of the Splunk Add-on Builder ...

Solve, Learn, Repeat: New Puzzle Channel Now Live

Welcome to the Splunk Puzzle PlaygroundIf you are anything like me, you love to solve problems, and what ...

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...