# Using keystore in curator

**URL:** <https://discuss.elastic.co/t/using-keystore-in-curator/200610>\
**Category:** Elasticsearch\
**Created:** [September 23, 2019, 12:31am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610 "2019-09-23T00:31:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cowensel](https://avatars.discourse-cdn.com/v4/letter/c/eb9ed0/32.png) [@cowensel](https://discuss.elastic.co/u/cowensel)\
**Post date:** [September 23, 2019, 12:31am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/1 "2019-09-23T00:31:39Z")

</div>

Hi There,

Does anyone use Curator where the username and password are stored in a keystore rather than being plain text in the config file. I need to try and avoid passwords in plain text in configuration files.

Any suggestions would be helpful.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [September 23, 2019, 12:53am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/2 "2019-09-23T00:53:49Z")

</div>

This functionality does not yet exist in Curator, but has been requested.

---

<div class="post-metadata">

**Author:** ![cowensel](https://avatars.discourse-cdn.com/v4/letter/c/eb9ed0/32.png) [@cowensel](https://discuss.elastic.co/u/cowensel)\
**Post date:** [September 23, 2019, 7:24am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/3 "2019-09-23T07:24:36Z")

</div>

Thank you theuntergeek.

Do you know what permissions a user needs to run curator. I would like to limit the user to have the permissions necessary to run curator and nothing else.

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [September 30, 2019, 4:45am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/4 "2019-09-30T04:45:06Z")

</div>

Curator itself needs no permissions other than outbound TCP access to the cluster IP and port.

However, if you have Security enabled in your cluster, the user Curator connects to the cluster as must have the proper roles/permissions for the actions being executed.

---

<div class="post-metadata">

**Author:** ![cowensel](https://avatars.discourse-cdn.com/v4/letter/c/eb9ed0/32.png) [@cowensel](https://discuss.elastic.co/u/cowensel)\
**Post date:** [September 30, 2019, 6:21am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/5 "2019-09-30T06:21:10Z")

</div>

Thank you for letting me know.

---

<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:** [October 28, 2019, 6:21am UTC](https://discuss.elastic.co/t/using-keystore-in-curator/200610/6 "2019-10-28T06:21:44Z")

</div>

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