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 Fri, 04 Nov 2016 14:08:59 GMT

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

ASF GitHub Bot commented on FLINK-3930:
---------------------------------------

Github user StephanEwen commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2425#discussion_r86543115
  
    --- Diff: docs/internals/flink_security.md ---
    @@ -84,4 +86,79 @@ Security implementation details are based on <a href="https://github.com/apache/
     
     ## Token Renewal
     
    -UGI and Kafka/ZK login module implementations takes care of auto-renewing the tickets
upon reaching expiry and no further action is needed on the part of Flink.
    \ No newline at end of file
    +UGI and Kafka/ZK login module implementations takes care of auto-renewing the tickets
upon reaching expiry and no further action is needed on the part of Flink.
    +
    +# Authorization Support
    --- End diff --
    
    How about elaborating a bit on the interplay between the Authorization and Encryption
support? For example, it is important to know that secrets go plain text over every wire unless
encryption is enabled.


> 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)

Mime
View raw message