[
https://issues.apache.org/jira/browse/AMBARI-12916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185448#comment-15185448
]
Alejandro Fernandez commented on AMBARI-12916:
----------------------------------------------
My concern is that this is a global change and it should be consistent.
Can you confirm that the following will still work after changing the server
host name,
1. Views (which still use DNS to resolve the ambari server hostname, and may
then receive a URI for how to hit the APIs).
2. APIs (we have a lot of href objects, so these should also use the changed
ambari server hostname).
> 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)
