[AMBARI-11694] After enabling Kerberos via the REST API, the Ambari UI behaves as if the cluster is not Kerberized

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.0
• Component/s: ambari-web
• Assignee: Antonenko Alexander
• Reporter: Antonenko Alexander
• Created: 04/Jun/15 15:43
• Updated: 04/Jun/15 18:54
• Resolved: 04/Jun/15 15:50

Description

After enabling Kerberos via the REST API, the Ambari UI behaves as if the cluster is not Kerberized - even after restarting Ambari.

Possibly related is the following logged messages in the ambari-server.log:

23 Apr 2015 11:30:22,605  INFO [pool-3-thread-132] URLStreamProvider:181 - Received WWW-Authentication header:Negotiate, for URL:http://ambari.vagrant.tgt:8744/api/v1/cluster/summary
23 Apr 2015 11:30:22,610  WARN [pool-3-thread-132] RequestTargetAuthentication:88 - NEGOTIATE authentication error: No valid credentials provided (Mechanism level: No valid credentials provided (Mechanism level: Attempt to obtain new INITIATE credentials failed! (null)))
23 Apr 2015 11:30:22,611 ERROR [pool-3-thread-132] AppCookieManager:122 - SPNego authentication failed, can not get hadoop.auth cookie for URL: http://ambari.vagrant.tgt:8744/api/v1/cluster/summary