All Apps and Add-ons

About the settings of identities.conf in the SHC environment

yutaka1005
Builder

Splunk ver 7.5.2
DB connect 3.1.4
SHC's member 3 (* include captain)

When a new identity is created, identities.conf is created, but PW is hashed.

If I do similar operations in one of the SHC members, they replicate identities.conf(* PW is hashed by logic in one of SHC members where I create identity.), but the PW hash value should be created with each Splunk's logic, so one will work fine But the remaining two will be in error.

Also, if I distribute from deployer, it will enter default, so it will disappear when I update DB connect next time.

What should I do?

0 Karma
1 Solution

yutaka1005
Builder

According to the following, I let all members had the same identity.dat, then it worked without problems.

https://answers.splunk.com/answers/306846/splunk-db-connect-2-identities-and-connections-not.html

View solution in original post

0 Karma

yutaka1005
Builder

According to the following, I let all members had the same identity.dat, then it worked without problems.

https://answers.splunk.com/answers/306846/splunk-db-connect-2-identities-and-connections-not.html

0 Karma
Get Updates on the Splunk Community!

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...

Splunk App Developers | .conf25 Recap & What’s Next

If you stopped by the Builder Bar at .conf25 this year, thank you! The retro tech beer garden vibes were ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...