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!

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...