You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Greg Hill (JIRA)" <ji...@apache.org> on 2015/09/01 14:58:46 UTC

[jira] [Commented] (AMBARI-12916) Make API server hostname for views configurable

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

Greg Hill commented on AMBARI-12916:
------------------------------------

I've attached a potential patch.  I need to figure out how to run the tests still, but I'll adjust the patch with tests when I do.  In the interim, if there's anything obviously wrong with the approach, let me know.

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