[
https://issues.apache.org/jira/browse/NIFI-12140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773781#comment-17773781
]
ASF subversion and git services commented on NIFI-12140:
--------------------------------------------------------
Commit 5a42d7245b6e852c99c068fa34f991f0c6d80b3b in nifi's branch
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5a42d7245b ]
NIFI-12140 Add optional properties to RedisConnectionPoolService for Username
and Sentinel Username (#7862)
> Possibility to configure ACLs for redis connections
> ---------------------------------------------------
>
> Key: NIFI-12140
> URL: https://issues.apache.org/jira/browse/NIFI-12140
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.21.0
> Reporter: Fabian Reiber
> Assignee: Bryan Bende
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The RedisConnectionPoolService and RedisDistributedMapCacheClientService do
> not allow to configure acls. At least I can't find it. Is this a feature to
> be added in near future?
> The current possibility to configure a password in RedisConnectionPoolService
> reflects the "requirepass" in redis configuration. It also means to enable
> acls configuration for redis sentinel as well. And maybe for redis cluster
> too (I don't know, if redis cluster uses different acls as well)?
> I think it makes sense to enable this feature for
> RedisDistributedMapCacheClientService.
> What do you think about it?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)