title: Issue on Hadoop CDH4.1.2 configuring with kerberos
body: <p><strong>My datanode log file:</strong></p>
  
  <p><code>*2013-01-28 22:12:05,084 WARN org.apache.hadoop.ipc.Client: Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
  2013-01-28 22:12:05,084 ERROR org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:dr.who (auth:KERBEROS_SSL) cause:java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]*</code></p>
  
  <p>I have started installing hadoop CDH4.1.2 with kerberos, and datanode is started as secure process.</p>
  
  <p>As per <a href="https://ccp.cloudera.com/display/CDH4DOC/Configuring+Hadoop+Security+in+CDH4" rel="nofollow">https://ccp.cloudera.com/display/CDH4DOC/Configuring+Hadoop+Security+in+CDH4</a>
  <a href="https://ccp.cloudera.com/display/CDH4DOC/Appendix+A+-+Troubleshooting#AppendixA-Troubleshooting-Problem2" rel="nofollow">https://ccp.cloudera.com/display/CDH4DOC/Appendix+A+-+Troubleshooting#AppendixA-Troubleshooting-Problem2</a></p>
  
  <p>the above links i understood that hadoop command line is unable to get the credentials for the kerberos ticket, so a workaround is suggested to renew the ticket. Yes, the workaround solves the command line problem, i can access the HDFS.</p>
  
  <p>But from the Namenode UI, i cannot view the logs, it shows HTTP 401 ERROR.
  <code>**User dr.who is unauthorized to access this page.**</code></p>
  
  <p>Has anyone faced this issue ?</p>
  
  <p>Thanks in advance</p>