UI Behavior for Non-Kerberized Clusters
The contents of the Hadoop Authentication tab change depending on whether the cluster is kerberized.
For a secure cluster with Kerberos enabled, the Hadoop
Authentication tab displays a Kerberos section with
fields to enter your Kerberos principal and username. However, if Cloudera Data Science
Workbench cannot detect a
krb5.conf file on the host, it will assume the
cluster is not kerberized, and the Hadoop Authentication tab will
display Hadoop Username Override configuration instead.
For a non-kerberized cluster, by default, your Hadoop username will be
set to your Cloudera Data Science Workbench username. To override this
default and set an alternative
HADOOP_USER_NAME, go to
the Hadoop Username Override setting at
If the Hadoop Authentication tab is incorrectly
displaying Kerberos configuration fields for a non-kerberized cluster,
make sure the
krb5.conf file is not present on the host
running Cloudera Data Science Workbench. If you do find any instances of
krb5.conf on the host, depending on your deployment,
perform one of the following sets of actions:
On CSD deployments, go to Cloudera Manager and stop the CDSW service. Remove the
krb5.conffile(s) from the Cloudera Data Science Workbench gateway host, and then start the CDSW in Cloudera Manager.
On RPM deployments, run
cdsw stop, remove the
krb5.conffile(s) from the Cloudera Data Science Workbench gateway host, and run
You should now see the expected Hadoop Username Override configuration field.
Cloudera Data Science Workbench does not support the use of Kerberos plugin modules in