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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

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

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...