[
https://issues.apache.org/jira/browse/FLINK-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468482#comment-15468482
]
ASF GitHub Bot commented on FLINK-3930:
---------------------------------------
Github user rmetzger commented on the issue:
https://github.com/apache/flink/pull/2425
Thank you for addressing my comments.
I've looked into the design document [1] again and some details are missing
there. In particular its not clearly specified how and where the shared secrets
are created and transferred in the cluster.
How is the secret transferred to the TaskManagers on YARN?
Is the using the `JobManagerMessages.getRequestBlobManagerSecureCookie()`
message always secure?
I think its important for security-related changes to first have a clear,
documented security concept, and then an implementation that matches the
documentation.
Maybe it also makes sense to start adding a page into the internals
documentation section, explaining how the secure cookie is implemented.
@StephanEwen can you maybe add your thoughts here?
[1]
https://docs.google.com/document/d/1-GQB6uVOyoaXGwtqwqLV8BHDxWiMO2WnVzBoJ8oPaAs/edit
> Implement Service-Level Authorization
> -------------------------------------
>
> Key: FLINK-3930
> URL: https://issues.apache.org/jira/browse/FLINK-3930
> Project: Flink
> Issue Type: New Feature
> Components: Security
> Reporter: Eron Wright
> Assignee: Vijay Srinivasaraghavan
> Labels: security
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> _This issue is part of a series of improvements detailed in the [Secure Data
> Access|https://docs.google.com/document/d/1-GQB6uVOyoaXGwtqwqLV8BHDxWiMO2WnVzBoJ8oPaAs/edit?usp=sharing]
> design doc._
> Service-level authorization is the initial authorization mechanism to ensure
> clients (or servers) connecting to the Flink cluster are authorized to do so.
> The purpose is to prevent a cluster from being used by an unauthorized
> user, whether to execute jobs, disrupt cluster functionality, or gain access
> to secrets stored within the cluster.
> Implement service-level authorization as described in the design doc.
> - Introduce a shared secret cookie
> - Enable Akka security cookie
> - Implement data transfer authentication
> - Secure the web dashboard
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
