Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 4 Nov 2016 14:08:59 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12970914.1463604092000.188939.1478268539233@Atlassian.JIRA>
In-Reply-To: <JIRA.12970914.1463604092000@Atlassian.JIRA>
References: <JIRA.12970914.1463604092000@Atlassian.JIRA> <JIRA.12970914.1463604092980@arcas>
Subject: [jira] [Commented] (FLINK-3930) Implement Service-Level
 Authorization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 04 Nov 2016 14:09:01 -0000


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

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_r86550433
  
    --- Diff: flink-core/src/main/java/org/apache/flink/configuration/GlobalConfiguration.java ---
    @@ -144,8 +144,15 @@ private static Configuration loadYAMLResource(File file) {
     						continue;
     					}
     
    -					LOG.debug("Loading configuration property: {}, {}", key, value);
     					config.setString(key, value);
    +
    +					//to prevent logging the secure cookie
    +					if(key.equals(ConfigConstants.SECURITY_COOKIE) && value != null) {
    +						value = "******";
    --- End diff --
    
    Can all suppressed keys have a common prefix?
    
    This should also be guarded by a test ;-)


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