Splunk Search

Security Key in server.conf

nawazns5038
Builder

what is the diff between the security key in the clustering stanza and the key in the general stanza in server.conf ?

Should the same key be used for both the shcluster and the indexer cluster ?

Tags (1)
0 Karma
1 Solution

horsefez
Motivator

Hi,

so the server.conf general key is a unique key that get's generated on first startup. It will be "salted" with a server unique value. Don't use this one for clustering.

For indexer clustering you should use an identical passphrase on all servers.
Something like: "applepie" ... which then after a restart gets converted into a hash using the server unique "salt" again.

You can use a different one for SH-Cluster, but you don't have to.

The important part is that you don't copy the "hashed" value... you should manually set the cleartext password and then restart the system.

View solution in original post

horsefez
Motivator

Hi,

so the server.conf general key is a unique key that get's generated on first startup. It will be "salted" with a server unique value. Don't use this one for clustering.

For indexer clustering you should use an identical passphrase on all servers.
Something like: "applepie" ... which then after a restart gets converted into a hash using the server unique "salt" again.

You can use a different one for SH-Cluster, but you don't have to.

The important part is that you don't copy the "hashed" value... you should manually set the cleartext password and then restart the system.

Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

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

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...