# Possible Feature Request: Redis Authentication with Username/Password **URL:** \ **Category:** Logstash\ **Created:** [August 8, 2023, 9:25am UTC](https://discuss.elastic.co/t/possible-feature-request-redis-authentication-with-username-password/340349 "2023-08-08T09:25:01Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![alces](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alces/32/58340_2.png) [@alces](https://discuss.elastic.co/u/alces)\ **Post date:** [August 8, 2023, 9:25am UTC](https://discuss.elastic.co/t/possible-feature-request-redis-authentication-with-username-password/340349/1 "2023-08-08T09:25:01Z")
Hi everyone. We are planing to use redis between beats and logstash as a buffer for high utilization timespots. In this setup currently there is only a "password" option for the redis output/input plugin, so every participant can write AND READ the logs using the same default user. Therefore a corrupted host could read all current logs out of redis. As with redis 7.0.11 there is an option to only permit write access to redis, preventing a corrupt host of reading logs from other participants. In the most simple way we could restrict the default user to write only and add a new user for logstash to read, write etc. With this approach only a change to the logstash redis input would be needed: add username/password authentication. An ideal addition would be also adding username/password to redis output of all beats. Are we approaching things the wrong way or is this a valid feature request? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 5, 2023, 9:25am UTC](https://discuss.elastic.co/t/possible-feature-request-redis-authentication-with-username-password/340349/2 "2023-09-05T09:25:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.