[
https://issues.apache.org/jira/browse/APEXCORE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095695#comment-16095695
]
Sanjay M Pujare commented on APEXCORE-760:
------------------------------------------
Agreed it's a security hole and it's difficult to get public certs with
non-FQDN names (https://www.digicert.com/internal-names.htm) but wildcard and
alternate names seem to be a common work-around where non-public certs are used
in an internal network. But I do think (like you do) that with proper host
configuration it is possible to get the FQDN in the tracking URL so this JIRA
should be treated as an enhancement.
> Webapp tracking URL does not include fully qualified hostname
> -------------------------------------------------------------
>
> Key: APEXCORE-760
> URL: https://issues.apache.org/jira/browse/APEXCORE-760
> Project: Apache Apex Core
> Issue Type: Bug
> Affects Versions: 3.6.0
> Reporter: Thomas Weise
> Assignee: Thomas Weise
>
> The app master tracking URL that gets registered with the RM does not contain
> the full name, leading to mismatch in SSL certificate check.
> Instead of https://host:34112 it should be https://host.domain.com:34112
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
