You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/02/15 23:35:00 UTC
[jira] [Created] (GEODE-4691) Gfsh command Start Locator shows
inconsistent behavior with auto-connecting when a Security Manager
Barbara Pruijn created GEODE-4691:
-------------------------------------
Summary: Gfsh command Start Locator shows inconsistent behavior with auto-connecting when a Security Manager
Key: GEODE-4691
URL: https://issues.apache.org/jira/browse/GEODE-4691
Project: Geode
Issue Type: Bug
Components: docs, gfsh, security
Reporter: Barbara Pruijn
When starting a locator in gfsh like this
{code:java}
start locator --name=locator1{code}
the default behavior is to auto-connect gfsh to the locator.
From the gfsh start locator help:
{code:java}
connect
When connect is set to false , Gfsh does not automatically connect to the locator which is started
using this command.
Required: false
Default (if the parameter is specified without value): true
Default (if the parameter is not specified): true{code}
When starting the locator with a Security Manager like this
{code:java}
start locator --name=locator1 --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
The result is that gfsh does not auto connect to the locator. However this is not listed in the help command and is inconsistent in the user expectation.
Possible solutions:
1. Update gfsh help to correctly list the behavior when the Security Manager is set via the --J parameter
2. Add the options
{code:java}
--user --password{code}
to the start listener command
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)