You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Ernest Burghardt (Jira)" <ji...@apache.org> on 2021/09/09 18:56:00 UTC

[jira] [Resolved] (GEODE-9139) SSLException in starting up a Locator

     [ https://issues.apache.org/jira/browse/GEODE-9139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ernest Burghardt resolved GEODE-9139.
-------------------------------------
      Assignee: Kamilla Aslami  (was: Ernest Burghardt)
    Resolution: Fixed

> 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: Kamilla Aslami
>            Priority: Major
>              Labels: 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)