# Azure redis - password in yml file

**URL:** <https://discuss.elastic.co/t/azure-redis-password-in-yml-file/112362>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 19, 2017, 6:56am UTC](https://discuss.elastic.co/t/azure-redis-password-in-yml-file/112362 "2017-12-19T06:56:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [December 19, 2017, 6:56am UTC](https://discuss.elastic.co/t/azure-redis-password-in-yml-file/112362/1 "2017-12-19T06:56:58Z")

</div>

Dear all,

I could successfully set azure redis as output of filebeat. But I have some concerns in keeping password plain text in .yml file. Though ssl.enabled is set to true' and the n/w transmission is secured - keeping plain text password in .yml is treated as threat.

Any recommendations would be very helpful.

In logstash, ssl options itself is not there. I need to consume the data from redis @ logstash ☹

Regarsd  
Karthik R

---

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [December 19, 2017, 2:31pm UTC](https://discuss.elastic.co/t/azure-redis-password-in-yml-file/112362/2 "2017-12-19T14:31:18Z")

</div>

Hi Karthik,

We are actively working on having a safe-store for passwords in Filebeat.

As a first step, you can take a look at [this pull request](https://github.com/elastic/beats/pull/5687) that allows storing obfuscated passwords in a local keystore.

---

<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:** [January 16, 2018, 2:31pm UTC](https://discuss.elastic.co/t/azure-redis-password-in-yml-file/112362/3 "2018-01-16T14:31:35Z")

</div>

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