Deployment Architecture

Changing the pass4SymmKey for Search Head Clustering not being encrypted in the Deployer


We were having trouble with one of the Search Head cluster members. We went in to ensure that all of the shclustering pass4SymmKey values were correct. After restarting the Deployer splunkd service we found that the value for the pass4SymmKey did not get encrypted. Other pass4SymmKeys are being encrypted (clustering and general) but not the shclustering. This has happened on both 6.4.0 and 6.4.1 versions.

We double checked that the field was listed in the encrypt fields and it is.

I'm figuring we are missing something. Any suggestions?

0 Karma


Is your server.conf containing the cleartext pass4symmkey in a 'default' directory? If so it will be left in cleartext and the hashed version will be written in the corresponding local/server.conf

This is described under "How pass4SymmKey gets encrypted in apps"

0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...