[
https://issues.apache.org/jira/browse/AMBARI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183526#comment-15183526
]
Robert Levas commented on AMBARI-12916:
---------------------------------------
[~jimbobhickville]. I am concerned with _faking_ the Ambari server's
hostname. There is lots of code that relies on the FQDN of the host that the
Ambari server executes on and if we allow for an additional name to be used,
than we will wind up with some interesting scenarios.
My main concern is with Kerberos-related tasks where the _discovered_ FQDN of
the host is used for many things. However the effects on other parts of Ambari
may take a while to uncover. For example each view. Who will be tasked with
testing each view to make sure nothing breaks when an alternate host name is
used to access the API?
Can you describe a valid use case for this?
> Make API server hostname for views configurable
> -----------------------------------------------
>
> Key: AMBARI-12916
> URL: https://issues.apache.org/jira/browse/AMBARI-12916
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server, ambari-views
> Affects Versions: 2.1.0
> Reporter: Greg Hill
> Assignee: Greg Hill
> Priority: Minor
> Attachments: AMBARI-12916.patch
>
>
> The views that need to get data from the Ambari API use the system hostname
> to connect to the Ambari API. The problem is that the API could be
> configured with an SSL cert for a domain name other than the system hostname,
> and if you connect to it using the hostname, you will get SSL validation
> errors. Simply adding an optional hostname to the Ambari configs that will
> be used here would make it much easier to work in this sort of setup.
> https://github.com/apache/ambari/blob/4c73ea906d02df2c79ef76f5cf6fd2b94ea78ca6/ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java#L299
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
