[
https://issues.apache.org/jira/browse/HBASE-14700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977281#comment-14977281
]
Gary Helmling commented on HBASE-14700:
---------------------------------------
Hi [~appy], yes, as you note, there are some problems with trying to use the
client-side fallback configuration to achieve the same goal:
# Until security is actually configured on the server-side, you are not
actually testing the client-side secure configuration. This allows for
configuration errors which are not discovered until the server-side security is
enabled.
# Enabling server-side security would require a complete cluster shutdown,
which may be undesirable.
I believe that allowing the fallback to be configured on and off on the
server-side allows a more incremental approach to rollout, especially in cases
where many clients may be using a cluster, each requiring their own changes and
testing.
I think in theory this could even allow enabling secure configuration on the
server-side on a rolling basis.
I'll post a patch for review shortly.
> 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
>
> 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)
