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

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

I'm not faking anything.  The server has two hostnames, one for local cluster 
traffic, one for public traffic.  The SSL cert for the Ambari API matches the 
public fqdn, but the way that Ambari resolves the hostname returns the local 
cluster hostname.  Now we have a cert mismatch and the views don't work.  

This code path is only used by the views, and it's returning the URI for the 
ambari server that the views can use to contact the ambari API.   It doesn't 
even purport to return the hostname, and the Kerberos code doesn't utilize it.  
I want to tell Ambari what URI to use, because it makes sense to allow this for 
ambiguous cases like this.  

I think the name of the variable being masterHostname is what is throwing this 
off.  That's only used by getAmbariServerURI() in the existing codebase, which 
is only exposed to the views.  I think you're confusing it with 
conf.getMasterHostname()

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

Reply via email to