# Elastic bootstrap password not picked up by second cluster member

**URL:** <https://discuss.elastic.co/t/elastic-bootstrap-password-not-picked-up-by-second-cluster-member/246508>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [August 26, 2020, 8:17pm UTC](https://discuss.elastic.co/t/elastic-bootstrap-password-not-picked-up-by-second-cluster-member/246508 "2020-08-26T20:17:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cotjoey](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@cotjoey](https://discuss.elastic.co/u/cotjoey)\
**Post date:** [August 26, 2020, 8:17pm UTC](https://discuss.elastic.co/t/elastic-bootstrap-password-not-picked-up-by-second-cluster-member/246508/1 "2020-08-26T20:17:39Z")

</div>

I enabled security on my ELK stack. I tested the configuration locally several times before going on the dev environment. On the second master node of my cluster, I get the following error:

```auto
[2020-08-26T16:54:40,203][INFO][o.e.x.s.a.AuthenticationService] [master-node-2] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

```

I followed the steps:

1. Ran the elasticsearch-keystore command on the first master node:  
`printf "%s" "mypassword" | /usr/share/elasticsearch/bin/elasticsearch-keystore add -x "bootstrap.password"`
2. Ran the curl command to set the built-in user passswords.

Can you help explain why the 2nd master node in my cluster won't recognize the elastic bootstrap password set on master node1?

Thank you,  
Joey

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 23, 2020, 8:17pm UTC](https://discuss.elastic.co/t/elastic-bootstrap-password-not-picked-up-by-second-cluster-member/246508/2 "2020-09-23T20:17:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
