[ 
https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503833#comment-15503833
 ] 

Robert Levas commented on AMBARI-17898:
---------------------------------------

For the HTTP protocol, it is expected at the web-server side of the equation 
uses HTTP/_HOST, but the client side should use a relevant identity.  In this 
case the client should use something like {{ams/_HOST}} or 
{{ams_monitor/_HOST}}.


> Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-17898
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17898
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.2.0
>            Reporter: Qin Liu
>            Assignee: Qin Liu
>             Fix For: trunk
>
>         Attachments: AMBARI-17898.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to 
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari 
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But 
> Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does 
> not support Kerberos HTTP SPNEGO authentication.  
> /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out:
> 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: 
> http://metrics-collector:6188/ws/v1/timeline/metrics
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to 
> server. HTTP Error 401: Authentication required
> 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to