[
https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379547#comment-17379547
]
ASF subversion and git services commented on GEODE-9139:
--------------------------------------------------------
Commit c4b0876da035b568ff579e4c502768278999850c in geode's branch
refs/heads/support/1.14 from Naburun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c4b0876 ]
Revert "GEODE-9139 SSLException in starting up a Locator (#6308)(#6401)"
This reverts commit 863835969db3b5408764887aeeaf3b6943040c68.
> SSLException in starting up a Locator
> -------------------------------------
>
> Key: GEODE-9139
> URL: https://issues.apache.org/jira/browse/GEODE-9139
> Project: Geode
> Issue Type: Bug
> Components: membership, messaging
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.15.0
>
>
> If you start up a locator using its host name, without a domain name, as a
> bind address you may get an SSLException in the form
> {noformat}
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching hostname.domainname found
> {noformat}
> The LocatorLauncher and InternalLocator throw away the bind address string
> and later do a reverse lookup to find the fully qualified hostname to use in
> endpoint identification matching. If the locator's own TLS certificate
> doesn't have the fully qualified name in it as a Subject Alternate Name the
> connection that the Locator makes to its own location service will fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
