Disabling Kerberos

[#1]

Hi all,

We have a Kerberized cluster,but at the moment we would disable it.

How is it possible ?

I performed the following steps:

• Zookeeper -> enableSecurity (Enable Kerberos Authentication)-> false

• HDFS -> hadoop.security.authentication -> Simple
• HDFS -> hadoop.security.authorization -> false
• HDFS -> dfs.datanode.address -> from 1004 (for Kerberos) to 50010 (default)
• HDFS -> dfs.datanode.http.address  -> from 1006 (for Kerberos) to 50075 (default)
• HDFS -> Data Directory Permissions -> from 700 to 755

• HBASE -> hbase.security.authentication -> Simple
• HBASE -> hbase.security.authorization -> false

But when I start the cluster I have problems on Hue and Solr

Hue: It seems that Kerberos is still configured for Hue 

        -> The Kerberos Ticket Renewer is not running. How can i disable it? 

        ->  Impala e Oozie don't run from Hue

Solr:  

Caused by: java.io.IOException: Failed on local exception: java.io.IOException: Server asks us to fall back to SIMPLE auth, but this client is configured to only allow secure connections.;

I noticed that Hue and Solr run in secure mode. How can I disable them ?

Thanks

Alessio

[#2]

Just like other services. Pls look carefully ,you will find the botton. I have done this many times.

[#3]

Don't forget redeploy client. It's important

[#4]

Hi, 

I didn't find the button on CDH 5.1.2 but i removed the Kerberos Ticket Renewer and redeployed client.

I missed this for Solr

SOLR -> Solr Secure Authentication -> Simple

Thanks 

[#5 · Accepted solution]

You would work your way back through the security guide discussion on enabling kerberos:

http://www.cloudera.com/content/cloudera/en/documentation/cloudera-manager/v5-latest/Configuring-Had...

Note that if HBASE, or NN HA or JT HA was configured after enabling security, the cleanup can be difficult, the Znode paths within zookeeper might require manual removal of the ACL statements.

Todd

[#6]

Thanks,

I followed the instructions in reverse order, present on the link.

When I disabled Kerberos, I had the two Namenodes (HA) both in stand-by state and I removed manually entries in Zookeeper.

Now it works!!!

Thanks

Alessio

[#7]

Hi,

I have another question about this.

when you said :

Note that if HBASE, or NN HA or JT HA was configured after enabling security, the cleanup can be difficult, the Znode paths within zookeeper might require manual removal of the ACL statements.

The same problem can be present for Yarn (HA).

I tried to find the 'yarn.resourcemanager.zk-auth' in the yarn-site.xml (/var/run/cloudera-scm-agent/process) in order to auth with Zookeper and remove the ACL statement but is not present this parameter.

I searched it into all folders XXX-yarn-RESOURCEMANAGER (also in the most recent) but I cannot find it

How can i solve this? At the moment I have Yarn not in HA and when I try to enable the HA, both ResourceManagers stay in Stand-by

Thanks

Alessio

[#8]

Solved !!! 

Thanks

Alessio

[#9]

How so? i have the same problem!   Both my Yarn HA services went into standby.

[#10]

Looking for how you removed it from zk..

[#11]

Hello Alessio,

I am facing the same problem could you please outline the steps you did for Yarn and Zookeeper.

Thanks

Deepak

[#12]

The link provided is now broken. Is there an update to it?

[#13]

Try this one:

http://www.cloudera.com/documentation/manager/5-1-x/Configuring-Hadoop-Security-with-Cloudera-Manage...

[#14]

Have the same problem, but after clean and reinstall cluster (using parcels). Error appears when oozie java action wrties to HDFS (runs from HUE). Earlier on this cluster was Kerberos, and I cleand all (I hope) directories from previous installation.

Here is a detailed message:

Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.JavaMain], main() threw exception, java.io.IOException:
Failed on local exception: java.io.IOException: Server asks us to fall back to SIMPLE auth, but this client is configured to only allow secure connections.; 
Host Details : local host is: "hadoop-05.xxx.xx/172.19.x.xxx"; destination host is: "hadoop-02.xxx.xx":8020; 
org.apache.oozie.action.hadoop.JavaMainException: java.io.IOException: Failed on local exception: java.io.IOException:
Server asks us to fall back to SIMPLE auth, but this client is configured to only allow secure connections.;
Host Details : local host is: "hadoop-05.xxx.xx/172.19.x.xxx"; destination host is: "hadoop-02.xxx.xx":8020;

[#15]

I have a similar problem wanted to turn off Kerberos, so did everythin (turn auth to simple, data node ports etc etc).
Now the cluster does not use Kerberos, HDFS and Hive and Impala works fine, BUT THE OPTION FOR ENABLE KERBEROS IS STILL GREYED
Any thoughts?
T