[
https://issues.apache.org/jira/browse/GEODE-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966599#comment-15966599
]
Jinmei Liao commented on GEODE-2775:
------------------------------------
The problem lies in the fact that when in the embedded mode, the useSSL flag of
pulse is not correctly set. Here is the workaround with the current release:
In the embedded mode:
* once a locator/server is started with ssl, go to the working directory of the
member and find the pulse.properties file. Change the property
"pulse.useSSL.manager" to true.
* restart the locator/server to pick up the change in the properties file, now
pulse should be able to connect.
In the standalone mode:
* follow this guide to set up the pulse.properties and pulsesecurity.properties
with the ssl information:
http://gemfirexd.docs.pivotal.io/1.3.1/userguide/manage_guide/pulse/quickstart.html
* remember to put "pulse.useSSL.manager=true" in the pulse.properties
> Pulse is not using certificate to connect to JMX when ssl is turned for jmx
> connection
> --------------------------------------------------------------------------------------
>
> Key: GEODE-2775
> URL: https://issues.apache.org/jira/browse/GEODE-2775
> Project: Geode
> Issue Type: Bug
> Components: pulse
> Affects Versions: 1.1.1
> Reporter: Jinmei Liao
>
> Steps to reproduce:
> 1) start a locator with a SecurityManager and with this property:
> ssl-enabled-components=jmx
> 2) start a browser and tries to login to pulse.
> Actual result: not able to log in using valid username/password
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
