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

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_r86546406
  
    --- Diff: docs/setup/config.md ---
    @@ -125,6 +125,28 @@ Kerberos ticket renewal is abstracted and 
automatically handled by the Hadoop/Ka
     
     For Kafka and ZK, process-wide JAAS config will be created using the 
provided security credentials and the Kerberos authentication will be handled 
by Kafka/ZK login handlers.
     
    +### Secure Cookie Authentication
    +
    --- End diff --
    
    How about keeping this brief ans instead linking to the proper docs.
    
    ```
    Flink supports configuring a *secure cookie* (a shared secret) to secure 
Flink processes.
    The secure cookie is used to authorize all access to and between Flink 
Processes.
    For more details, see [link to docs]
    ```


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

Reply via email to