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.