[
https://issues.apache.org/jira/browse/FLINK-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924235#comment-15924235
]
ASF GitHub Bot commented on FLINK-3930:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2425
Sorry for chiming in a bit late here with this more fundamental question.
I would like to understand from a security architecture, what additional
security this shared secret gives us:
- If there is no encryption, then this shared secret is not very secure,
as it can be sniffed from the network
- When there is encryption, isn't the current assumption that all parties
have access to the server-side certificate? Would that already be a form of
shared secret, meaning that certificate-based authentication as part of the SSL
handshake already covers the mechanism of a shared secret?
> 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.15#6346)
