[
https://issues.apache.org/jira/browse/GEODE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781443#comment-15781443
]
ASF subversion and git services commented on GEODE-419:
-------------------------------------------------------
Commit bbbbd385d63b604ffb549ebb206f5c68d192ab4f in geode's branch
refs/heads/develop from [~ukohlmeyer]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=bbbbd38 ]
GEODE-419: Added test to test that for ssl it fails over to javax properties.
> 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: client/server, configuration, security
> Reporter: Darrel Schneider
> Assignee: Udo Kohlmeyer
> 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)
