Josh Elser commented on HBASE-15814:

I think the biggest decision to make would be whether we should have one 
"Security" chapter which encompasses all relevant security banter (e.g. "core", 
thrift1, thrift2, REST) or if we should leave the Security to 
fundamental/"core" components, and leave security for each of the related 

The CDH docs do the former while the HBase Book does the latter which is why 
the CDH docs look so much more expansive (I think). Maybe a good minimal change 
would be to proactively call out the other sections in our Book's Security 
chapter? (e.g. "By the way, if you care about $service, read this chapter too")

> Miss important information in Document of HBase Security
> --------------------------------------------------------
>                 Key: HBASE-15814
>                 URL: https://issues.apache.org/jira/browse/HBASE-15814
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Heng Chen
>            Priority: Major
> I have deployed secure cluster recently, and found we miss important 
> information in http://hbase.apache.org/book.html#security
> Some configurations like 
> {code}
> <property>
>   <name>hbase.regionserver.kerberos.principal</name> 
>   <value>hbase/_h...@your-realm.com</value> 
> </property> 
> <property> 
>   <name>hbase.regionserver.keytab.file</name> 
>   <value>/etc/hbase/conf/hbase.keytab</value> 
> </property>
> <property> 
>   <name>hbase.master.kerberos.principal</name> 
>   <value>hbase/_h...@your-realm.com</value> 
> </property> 
> <property> 
> <name>hbase.master.keytab.file</name> 
> <value>/etc/hbase/conf/hbase.keytab</value> 
> </property>
> {code}
> And i found more detailed document in 
> http://www.cloudera.com/documentation/enterprise/5-5-x/topics/cdh_sg_hbase_authentication.html

This message was sent by Atlassian JIRA

Reply via email to