[
https://issues.apache.org/jira/browse/HBASE-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919347#comment-13919347
]
Jonathan Hsieh commented on HBASE-10646:
----------------------------------------
bq. The security features can mostly be enabled independently, although most
features depend on secure authentication and secure RPC.
My understanding is that secure rpc is a separate implementation from the
normal rpc today. Does "merging" the secure rpc into the normal rpc make sense
-- a negotiation at connection time and a runtime variable that says requires
or doesn't require secure rpc?
bq. For this JIRA, it could be sufficient to enable most of the security
features in the default configuration, excepting those which have, due to their
nature, a performance consequence.
Can we just have a single security == true or security == false config
property? For snapshots we added so that users only had to set that -- all the
various plugins required for it to work got added when snapshots.enabled was
set to true.
> Enable security features by default for 1.0
> -------------------------------------------
>
> Key: HBASE-10646
> URL: https://issues.apache.org/jira/browse/HBASE-10646
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.99.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
>
> As discussed in the last PMC meeting, we should enable security features by
> default in 1.0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
