[AMBARI-17898] Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: trunk
• Component/s: ambari-metrics
• Epic Link: AMSv0.2 Enhancements
• Assignee: Qin Liu
• Reporter: Qin Liu
• Created: 26/Jul/16 09:18
• Updated: 22/Aug/17 17:21
• Resolved: 22/Aug/17 17:21

Description

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 ...

Issue Links

• is related to: AMBARI-18896 Suse11 deployment failures due to package issues
• relates to: AMBARI-14384 Ambari Metrics doesn't use SPNEGO to authenticate
• links to: Review Board
• links to: ReviewBoard
• links to: ReviewBoard