[
https://issues.apache.org/jira/browse/FLINK-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272088#comment-17272088
]
Till Rohrmann commented on FLINK-21108:
---------------------------------------
Thanks for creating this issue [~xexplorer]. The recommended way for solving
this problem would be to place Flink's REST server and history server behind an
HTTP proxy which supports authentication. That way we can keep this
functionality out of Flink and thereby a bit slimmer. Moreover, there are
different ways for authentication and implementing this within Flink will
require sooner or later to also support all different types of authentication.
Hence, I would be in favour of keeping this functionality out of Flink. What do
you think?
> Flink runtime rest server and history server webmonitor do not require
> authentication.
> --------------------------------------------------------------------------------------
>
> Key: FLINK-21108
> URL: https://issues.apache.org/jira/browse/FLINK-21108
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / REST, Runtime / Web Frontend
> Reporter: Xiaoguang Sun
> Priority: Major
> Labels: pull-request-available
>
> Flink runtime rest server and history server webmonitor do not require
> authentication. At certain scenarios, prohibiting unauthorized access is
> desired. Http basic authentication can be used here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
