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!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...