Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 29 Oct 2015 23:27:27 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12908051.1445900351000.102174.1446161247825@Atlassian.JIRA>
In-Reply-To: <JIRA.12908051.1445900351000@Atlassian.JIRA>
References: <JIRA.12908051.1445900351000@Atlassian.JIRA>
 <JIRA.12908051.1445900351914@arcas>
Subject: [jira] [Commented] (HBASE-14700) Support a "permissive" mode for
 secure clusters to allow "simple" auth clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Elliott Clark commented on HBASE-14700:
---------------------------------------

Yeah test region mover is being worked on in HBASE-14718

> Support a "permissive" mode for secure clusters to allow "simple" auth clients
> ------------------------------------------------------------------------------
>
>                 Key: HBASE-14700
>                 URL: https://issues.apache.org/jira/browse/HBASE-14700
>             Project: HBase
>          Issue Type: Improvement
>          Components: security
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0
>
>         Attachments: HBASE-14700-v2.patch, HBASE-14700-v3.patch, HBASE-14700.patch
>
>
> When implementing HBase security for an existing cluster, it can be useful to support mixed secure and insecure clients while all client configurations are migrated over to secure authentication.  
> We currently have an option to allow secure clients to fallback to simple auth against insecure clusters.  By providing an analogous setting for servers, we would allow a phased rollout of security:
> # First, security can be enabled on the cluster servers, with the "permissive" mode enabled
> # Clients can be converting to using secure authentication incrementally
> # The server audit logs allow identification of clients still using simple auth to connect
> # Finally, when sufficient clients have been converted to secure operation, the server-side "permissive" mode can be removed, allowing completely secure operation.
> Obviously with this enabled, there is no effective access control, but this would still be a useful tool to enable a smooth operational rollout of security.  Permissive mode would of course be disabled by default.  Enabling it should provide a big scary warning in the logs on startup, and possibly be flagged on relevant UIs.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)