[
https://issues.apache.org/jira/browse/AMBARI-11694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573005#comment-14573005
]
Aleksandr Kovalenko commented on AMBARI-11694:
----------------------------------------------
+1 for the patch
> After enabling Kerberos via the REST API, the Ambari UI behaves as if the
> cluster is not Kerberized
> ---------------------------------------------------------------------------------------------------
>
> Key: AMBARI-11694
> URL: https://issues.apache.org/jira/browse/AMBARI-11694
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11694.patch
>
>
> 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:
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
