You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2016/02/06 00:14:39 UTC
[jira] [Updated] (GEODE-419) javax.net.ssl.* gemfire properties
ignored if ssl-enabled is false
[ https://issues.apache.org/jira/browse/GEODE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider updated GEODE-419:
-----------------------------------
Component/s: (was: core)
membership
> javax.net.ssl.* gemfire properties ignored if ssl-enabled is false
> ------------------------------------------------------------------
>
> Key: GEODE-419
> URL: https://issues.apache.org/jira/browse/GEODE-419
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Minor
>
> You are supposed to be able to put javax.net.ssl.* system property definitions in your gemfire.properties and have them be used to configure ssl.
> They work ok if ssl-enabled is true and cluster-ssl-enabled is not set. But if you set cluster-ssl-enabled (to true or false) then the javax.net.ssl.* properties are ignored. The same is also true for http-service-ssl-enabled.
> This can be worked around by using the new cluster-ssl-keystore* and cluster-ssl-truststore* gemfire properties instead of javax.net.ssl.*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)