So I setup a stand alone Splunk Environment and the choice was made to bind it with SSL. So we have https://BoxA that has all the roles.
We now have a brand new box that we would like to use as a Search head and we do NOT want to put SSL on this box. We would like to use BoxA as BoxB's License Master but each time i try to make the connection it throws an error
"Bad request - inhandler localslave edittracker failed reason = warn: path=/masterlm/usage;invalid signature on request
from IP: X.X.X.X
Do I have to setup the 2nd Box (BoxB) with SSL in order for it to join (become a license slave/ sh) for Box A. thanks
I can't find the existing answer to that question now, but here are some simple steps you could try:
Yes, I'm using it as you've said. I've set this up in other environments without issue. Never in mixed configuration.
I inherited this environment. it's possible that the previous person handjammed something he shouldn't into a config file.
8089 uses ssl by default unless you over-ride it in server.conf
from boxb what happens if you do:
openssl s_client -connect boxa:8089 -CAfile /opt/splunk/etc/auth/cacert.pem
There could be other issues as well, but I don't see the full picture here have you used: