[
https://issues.apache.org/jira/browse/GEODE-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374378#comment-16374378
]
ASF subversion and git services commented on GEODE-4691:
--------------------------------------------------------
Commit 7d7361cd1a211ce91f8aadc52deb7e6e63f8414c in geode's branch
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7d7361c ]
GEODE-4691: Gfsh command Start Locator shows inconsistent behavior wi… (#1478)
...th auto-connecting with a Security Manager
> Gfsh command Start Locator shows inconsistent behavior with auto-connecting
> with 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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.
>
> Solution and accceptance criteria:
> Update the output of
> {code:java}
> start locator
> --J=-Dgemfire.security-manager=org.apache.geode.examples.SimpleSecurityManager{code}
> to indicate that it is not auto-connected. New output:
> {code:java}
> Security Manager is enabled - unable to auto-connect. Please use connect with
> --user and --password to connect to locator.{code}
> Update gfsh help to correctly list the behavior when the Security Manager is
> set via the --J parameter
>
> gfsh should display correct connect help message for
> {code:java}
> help start locator{code}
> when using Security Manager.
> {code:java}
> connect
> When connect is set to false or when locator is started with a security
> manager using --J=-Dgemfire.security-manager option, 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}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
