[
https://issues.apache.org/jira/browse/FLINK-33376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780411#comment-17780411
]
Matthias Pohl edited comment on FLINK-33376 at 10/30/23 3:36 PM:
-----------------------------------------------------------------
Sounds like a good idea. We could think about utilizing the namespaces. The
FLIP could propose adding namespace support for {{curator}} -and
{{zookeeper}}-. That would allow to load any parameter supported by these
systems. WDYT?
was (Author: mapohl):
Sounds like a good idea. We could think about utilizing the namespaces. The
FLIP could propose adding namespace support for {{curator}} and {{zookeeper}}.
That would allow to load any parameter supported by these systems. WDYT?
> Add AuthInfo config option for Zookeeper configuration
> ------------------------------------------------------
>
> Key: FLINK-33376
> URL: https://issues.apache.org/jira/browse/FLINK-33376
> Project: Flink
> Issue Type: Improvement
> Reporter: Oleksandr Nitavskyi
> Assignee: Oleksandr Nitavskyi
> Priority: Major
>
> In certain cases ZooKeeper requires additional Authentication information.
> For example list of valid [names for
> ensemble|https://zookeeper.apache.org/doc/r3.8.0/zookeeperAdmin.html#:~:text=for%20secure%20authentication.-,zookeeper.ensembleAuthName,-%3A%20(Java%20system%20property]
> in order to prevent the accidental connecting to a wrong ensemble.
> Curator allows to add additional AuthInfo object for such configuration. Thus
> it would be useful to add one more additional Map property which would allow
> to pass AuthInfo objects during Curator client creation.
> *Acceptance Criteria:* For Flink users it is possible to configure auth info
> list for Curator framework client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
