You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "nabarun (JIRA)" <ji...@apache.org> on 2018/10/03 21:38:26 UTC
[jira] [Closed] (GEODE-5661) Pulse does not work when legacy SSL
options are used
[ https://issues.apache.org/jira/browse/GEODE-5661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nabarun closed GEODE-5661.
--------------------------
> Pulse does not work when legacy SSL options are used
> ----------------------------------------------------
>
> Key: GEODE-5661
> URL: https://issues.apache.org/jira/browse/GEODE-5661
> Project: Geode
> Issue Type: Bug
> Components: pulse
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Similar to GEODE-5230, if the legacy SSL configuration options are used, ({{cluster-ssl-*}}, {{jmx-manager-ssl-*}}, etc.), then Pulse does not work correctly and a user will see an error similar to the following in the UI:
> {noformat}
> Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)