drill-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] (DRILL-5671) Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster
Date Fri, 21 Jul 2017 22:48:00 GMT

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

ASF GitHub Bot commented on DRILL-5671:

Github user chunhui-shi commented on a diff in the pull request:

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/coord/zk/ZKACLProviderFactory.java
    @@ -0,0 +1,44 @@
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.drill.exec.coord.zk;
    +import org.apache.curator.framework.api.ACLProvider;
    +import org.apache.curator.framework.imps.DefaultACLProvider;
    +import org.apache.drill.common.config.DrillConfig;
    +import org.apache.drill.exec.ExecConstants;
    +public class ZKACLProviderFactory {
    +    static final org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(ZKACLProviderFactory.class);
    +    public static ACLProvider getACLProvider(DrillConfig config, String clusterId, String
zkRoot) {
    +        if (config.getBoolean(ExecConstants.ZK_SECURE_ACL)) {
    +            if (config.getBoolean(ExecConstants.USER_AUTHENTICATION_ENABLED)){
    +                logger.trace("ZKACLProviderFactory: Using secure ZK ACL");
    +                return new ZKSecureACLProvider(clusterId, zkRoot);
    +            } else {
    +                logger.warn("ZKACLProviderFactory : Secure ZK ACL enabled but user authentication
is disabled." +
    --- End diff --
    USER_AUTHENTICATION_ENABLED means the drill's client is logging in drill as some authenticated
users, but enabling zookeeper ACL means we are going to protect our znodes using ACL. so other
user should not be able to modify our znodes, I think this is a valid scenario, meaning no
warning needed.

> Set secure ACLs (Access Control List) for Drill ZK nodes in a secure cluster
> ----------------------------------------------------------------------------
>                 Key: DRILL-5671
>                 URL: https://issues.apache.org/jira/browse/DRILL-5671
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components:  Server
>            Reporter: Karthikeyan Manivannan
>            Assignee: Karthikeyan Manivannan
> All Drill ZK nodes, currently, are assigned a default [world:all] ACL i.e. anyone gets
to do CDRWA(create, delete, read, write, admin access). This means that even on a secure cluster
anyone can perform all CRDWA actions on the znodes. 
> This should be changed such that:
> - In a non-secure cluster, Drill will continue using the current default [world:all]
> - In a secure cluster, all nodes should have an [authid: all] ACL i.e. the authenticated
user that created the znode gets full access. The discovery znodes i.e. the znodes with the
list of Drillbits will have an additional [world:read] ACL, i.e. the list of Drillbits will
be readable by anyone. 

This message was sent by Atlassian JIRA

View raw message