Re: Question regarding WebHDFS security

Agree with Kris. Better off to start with Knox proxy auth, and then enable Kerberos within the cluster. Enabling Kerberos would still involve restarting of the services such as HDFS and Hive. I am not sure if there is a way to enable Kerberos without downtime. On Wed, Jul 6, 2016 at 5:22 PM,

Re: Question regarding WebHDFS security

Hi David, Looks like you are on the right track but you may have a hard time turning off Knox auth while the cluster without kerberos - at least I have never done this. Might be best to assume Knox authentication from the start and then you don't have to worry about it once the cluster is

Re: Question regarding WebHDFS security

Hi Ben, rather. :-) On Wed, Jul 6, 2016 at 6:21 PM, Kristopher Kane wrote: > Hi David, > > Looks like you are on the right track but you may have a hard time turning > off Knox auth while the cluster without kerberos - at least I have never > done this. Might be best

RE: Question regarding WebHDFS security

Hi Apache Knox devs, I've been in contact with Larry McCay to figure out a reasonable solution for my use case. I haven't gotten a chance to play around with Knox yet but in theory it will solve my problem - a three-phased upgrade should hopefully work. My specific use case is described

[jira] [Updated] (KNOX-720) Sockets remain in CLOSE_WAIT using org.apache.hadoop.gateway.shell.Hadoop

[ https://issues.apache.org/jira/browse/KNOX-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Battaglia updated KNOX-720: - Description: The class org.apache.hadoop.gateway.shell.Hadoop used to connect to knox doesn't

[jira] [Created] (KNOX-720) Sockets remain in CLOSE_WAIT using org.apache.hadoop.gateway.shell.Hadoop

Marco Battaglia created KNOX-720: Summary: Sockets remain in CLOSE_WAIT using org.apache.hadoop.gateway.shell.Hadoop Key: KNOX-720 URL: https://issues.apache.org/jira/browse/KNOX-720 Project: Apache