# Setting passwords for all built-in users

**URL:** <https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142>\
**Category:** Elasticsearch\
**Created:** [July 18, 2019, 7:47am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142 "2019-07-18T07:47:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hitesh\_Malhotra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitesh_malhotra/32/50434_2.png) [@Hitesh\_Malhotra](https://discuss.elastic.co/u/Hitesh_Malhotra)\
**Post date:** [July 18, 2019, 7:47am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/1 "2019-07-18T07:47:45Z")

</div>

Hi,

When I am trying to setup password for kibana user using below command

```
./bin/elasticsearch-setup-passwords interactive
I receive below error
 Unexpected response code [403] from calling GET http://127.0.0.1:9200/_xpack/security/_authenticate?pretty
It doesn't look like the X-Pack security feature is available on this Elasticsearch node.
Please check if you have installed a license that allows access to X-Pack Security feature.

ERROR: X-Pack Security is not available.

```

My Elasticsearch version is 6.5  
I have edited elasticsearch.yml as guided by sites

My question is:

1. Will I have to upgrade ELK stack to achieve security feature in BASIC License?
2. Is there any way to achieve security feature in BASIC License?

Thanks

---

<div class="post-metadata">

**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\
**Post date:** [July 18, 2019, 8:11am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/2 "2019-07-18T08:11:34Z")

</div>

> [@Hitesh\_Malhotra](#):
>
> My question is:
> 
> 1. Will I have to upgrade ELK stack to achieve security feature in BASIC License?
> 2. Is there any way to achieve security feature in BASIC License?
> 
> Thanks

1. Yes to at least 6.8.
2. Yes by using at least version 6.8.

---

<div class="post-metadata">

**Author:** ![Hitesh\_Malhotra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitesh_malhotra/32/50434_2.png) [@Hitesh\_Malhotra](https://discuss.elastic.co/u/Hitesh_Malhotra)\
**Post date:** [July 18, 2019, 8:45am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/3 "2019-07-18T08:45:47Z")

</div>

Thanks @martinr_ubi

If I upgrade the version, Will this activity impact on existing indexes, documents and dashboards?  
or will I have to setup everything again?

Please share how can I upgrade it?

---

<div class="post-metadata">

**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\
**Post date:** [July 18, 2019, 9:11am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/4 "2019-07-18T09:11:13Z")

</div>

I'm sorry @Hitesh_Malhotra but I won't detail here how you should upgrade your ES stack and related components, that is not really a specific question with a specific answer 🙂

There are entire sections of the documentation dedicated to upgrading the stacks and the required components, you should refer to that. In your case it's 6.5 to 6.8 so it's a minor version upgrade, which are simpler than major version upgrade like when you'll go to 7.x.

See:

> **[Security for Elasticsearch is now free](https://www.elastic.co/blog/security-for-elasticsearch-is-now-free)**
>
> We are thrilled to announce that the core security features of the Elastic Stack -- like TLS encryption, RBAC, and both file and native authentication -- are now free.

  

> **[Secure Elasticsearch with TLS encryption and role-based access control](https://www.elastic.co/blog/getting-started-with-elasticsearch-security)**
>
> Secure your Elasticsearch clusters -- and the other components of the Elastic Stack -- with node-to-node TLS and role-based access control (RBAC). These features and more are now available free with the default distribution of Elasticsearch and...

  
[https://www.elastic.co/guide/en/elasticsearch/reference/6.8/setup-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/setup-upgrade.html)  
[https://www.elastic.co/guide/en/elastic-stack/6.8/index.html](https://www.elastic.co/guide/en/elastic-stack/6.8/index.html)  
[https://www.elastic.co/guide/en/elastic-stack-overview/6.8/elasticsearch-security.html](https://www.elastic.co/guide/en/elastic-stack-overview/6.8/elasticsearch-security.html)  
[https://www.elastic.co/guide/en/elasticsearch/reference/6.8/configuring-security.html](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/configuring-security.html)

Since your going from no security to security you should make sure to test before doing anything in prod because if you have no experience yet with setting up the security features... configuring them for the first time directly in prod after the upgrade might not be the best approach of course.  
Of course you know your environment and I don't, depends on the SLA/SLO of your stack.

---

<div class="post-metadata">

**Author:** ![Hitesh\_Malhotra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitesh_malhotra/32/50434_2.png) [@Hitesh\_Malhotra](https://discuss.elastic.co/u/Hitesh_Malhotra)\
**Post date:** [July 18, 2019, 10:10am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/5 "2019-07-18T10:10:10Z")

</div>

Hi,

These articles are really helpful.

I have upgraded the Elastic from 6.5 to 6.8. Will I have to upgrade kibana and Logstash versions also to achieve security feature.

Thanks

---

<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:** [August 15, 2019, 10:10am UTC](https://discuss.elastic.co/t/setting-passwords-for-all-built-in-users/191142/6 "2019-08-15T10:10:20Z")

</div>

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