Security

How to access https management port from my application when enablesplunkdSSL=true?

kartik13
Communicator

I am making a call from a node to a Splunk instance i.e. 8089 port which is running by default on https protocol and uses Splunk Default Certfiicate. So when I make changes to enableSplunkdSSL = false, I am able to access the the 8089 port from my application through http protocol, but when enable it to true with these configuration:

[sslConfig]
enableSplunkdSSL = true
sslKeysfilePassword = ***************
sslKeysfile = server.pem
caCertFile = cacert.pem
caPath = C:/Program Files/Splunk/etc/auth
requireClientCert =false
sslVerifyServerCert =false
certCreateScript = C:/Program Files/Splunk/bin/genSignedServerCert.py

I am not able to hit the the Splunk instance. It's giving me a node error. Does any body know what is the issue here?

Thanks in advance

0 Karma
1 Solution

kartik13
Communicator

Its an certificate error.Self signed certificate error. So i allowed my webserver to make request to the self signed certificate https port, which by default is blocked as by the rules and regulation of CORS.
In node.js i added the following piece of code:
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

View solution in original post

0 Karma

kartik13
Communicator

Its an certificate error.Self signed certificate error. So i allowed my webserver to make request to the self signed certificate https port, which by default is blocked as by the rules and regulation of CORS.
In node.js i added the following piece of code:
process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

0 Karma
Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...