We had an app for called "orgfulllicenseserverssl" and it contains a server.conf
This server.conf has a parameter called "sslPassword".
Let say, the sslPassword is abcd1234 on this example.
So we had deploy the "orgfulllicenseserverssl" using the CM's master-apps, and it was push to the Peer nodes/IDX slave-apps.
We notice that the server.conf's parameter value for sslPassword is a readable "abcd1234". Do we have insights why it did not got hash on the first place?
Or is the best practice to move the "orgfulllicenseserverssl" from etc/slave-apps to etc/apps?
I am thinking, it might be the splunk.secret did not take effect if its on the etc/slave-apps
so the best practice to move the "orgfulllicenseserverssl" from etc/slave-apps to etc/apps and then restart it so it will be hash, correct?
I am having the same issue. Probably you can get the hash value on the CM, assuming it has the same certificate and splunk secret (which is used to encrypt the password), and plug the hash in the master app, then deploy the bundle to peers.