flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3930) Implement Service-Level Authorization
Date Tue, 06 Sep 2016 06:37:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466600#comment-15466600

ASF GitHub Bot commented on FLINK-3930:

Github user vijikarthi commented on the issue:

    T2-3 is not about the web interface netty, its about the data transfer netty
    In Flink, we are using netty for (at least) three things:
        - Akka is using Netty. This is addressed in the pull request
        - The web interface is using Netty. Addressed as well
        - The user data (datastreams, etc.) is transferred using Netty between the TaskManagers
as well.
    Thanks Robert for the clarification. It was a good catch and I have clearly missed the
Netty part used between TMs. I will create another JIRA and address the issue as part of it.

    I have incorporated your feedback comments and rebased the commits to latest master. Please
retest and see if the patch is okay?

> 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

View raw message