[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-9482:
-
Fix Version/s: (was: 0.94.13)
0.94.12
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.98.0, 0.94.12, 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch,
HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-9482:
-
Resolution: Fixed
Fix Version/s: 0.94.13
Status: Resolved (was: Patch Available)
Committed to 0.94 as well.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.98.0, 0.96.0, 0.94.13
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch,
HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Fix Version/s: 0.96.0
Affects Version/s: 0.95.2
0.94.11
Status: Patch Available (was: Open)
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482.patch
Patch for trunk.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Status: Open (was: Patch Available)
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482.patch
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Release Note: Seems that trunk code moved ahead since I generated the
patch. Resubmitting.
Status: Patch Available (was: Open)
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Status: Open (was: Patch Available)
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch,
HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482.patch
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch,
HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Release Note: (was: Seems that trunk code moved ahead since I generated
the patch. Resubmitting.)
Status: Patch Available (was: Open)
{{org.apache.hadoop.hbase.client.TestHCM.testConnection()}} creates an empty
configuration (from HBase perspective) and hence does not have value for
{{hbase.security.authentication}} set.
Resubmitting the patch.
Also, removing the ill placed comment in the release note section.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482.patch,
HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482-0.94.patch
Updated patch for 0.94 branch.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482-0.94.patch
Updated patch for 0.94 branch addressing [~ghelmling]'s comment.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482.patch
And for trunk.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch,
HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Status: Open (was: Patch Available)
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Release Note:
While it is possible to run secure HBase without securing underlying
filesystem, it is recommended that you run secure HBase on top of a secured
HDFS cluster to provide stronger guarantees of security. In such cases, you
must configure HBase services to be able to authenticate to HDFS services.
However, if the cluster hosting HBase service is protected via other means; for
example if it exports only HBase services to external users; you may save some
overhead by running secure HBase over unsecured HDFS. In such cases, you must
ensure that the HDSF services are not accessible to external user via any means.
Status: Patch Available (was: Open)
Submitting patch once again and adding release notes.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.94.11, 0.95.2
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch,
HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9482:
-
Fix Version/s: 0.98.0
Committed to 0.96 and 0.98 (thanks [~ghelmling]). [~lhofhansl] You want this
in 0.94 boss?
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Affects Versions: 0.95.2, 0.94.11
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Fix For: 0.98.0, 0.96.0
Attachments: HBASE-9482-0.94.patch, HBASE-9482-0.94.patch,
HBASE-9482-0.94.patch, HBASE-9482.patch, HBASE-9482.patch, HBASE-9482.patch,
HBASE-9482.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-9482) Do not enforce secure Hadoop for secure HBase
[
https://issues.apache.org/jira/browse/HBASE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated HBASE-9482:
--
Attachment: HBASE-9482-0.94.patch
Patch of 0.94 branch.
Do not enforce secure Hadoop for secure HBase
-
Key: HBASE-9482
URL: https://issues.apache.org/jira/browse/HBASE-9482
Project: HBase
Issue Type: Bug
Components: security
Reporter: Aditya Kishore
Assignee: Aditya Kishore
Labels: security
Attachments: HBASE-9482-0.94.patch
We should recommend and not enforce secure Hadoop underneath as a requirement
to run secure HBase.
Few of our customers have HBase clusters which expose only HBase services to
outside the physical network and no other services (including ssh) are
accessible from outside of such cluster.
However they are forced to setup secure Hadoop and incur the penalty of
security overhead at filesystem layer even if they do not need to.
The following code tests for both secure HBase and secure Hadoop.
{code:title=org.apache.hadoop.hbase.security.User|borderStyle=solid}
/**
* Returns whether or not secure authentication is enabled for HBase. Note
that
* HBase security requires HDFS security to provide any guarantees, so this
requires that
* both codehbase.security.authentication/code and
codehadoop.security.authentication/code
* are set to codekerberos/code.
*/
public static boolean isHBaseSecurityEnabled(Configuration conf) {
return kerberos.equalsIgnoreCase(conf.get(HBASE_SECURITY_CONF_KEY))
kerberos.equalsIgnoreCase(
conf.get(CommonConfigurationKeys.HADOOP_SECURITY_AUTHENTICATION));
}
{code}
What is worse that if {{hadoop.security.authentication}} is not set to
{{kerberos}} (undocumented at http://hbase.apache.org/book/security.html),
all other configuration have no impact and HBase RPCs silently switch back to
unsecured mode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
