You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Jinmei Liao (Jira)" <ji...@apache.org> on 2019/12/26 16:54:00 UTC

[jira] [Updated] (GEODE-7624) When gfsh is connected to an ssl-enabled locator, "status locator" command could be improved

     [ https://issues.apache.org/jira/browse/GEODE-7624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao updated GEODE-7624:
-------------------------------
    Description: When I connect to an ssl enabled locator, I already provided an --security-properties-file, once I am connected, I don't need to provide this option again when I am doing "status locator --name", it should use the same connection properties to do the tcp connection operation needed by the "status locator" command.  (was: When I connect to an ssl enabled locator, I already provided an --security-properties-file, once I am connected, I don't need to provide this option again when I am doing "status locator --name")

> When gfsh is connected to an ssl-enabled locator, "status locator" command could be improved
> --------------------------------------------------------------------------------------------
>
>                 Key: GEODE-7624
>                 URL: https://issues.apache.org/jira/browse/GEODE-7624
>             Project: Geode
>          Issue Type: Improvement
>          Components: gfsh
>            Reporter: Jinmei Liao
>            Priority: Major
>
> When I connect to an ssl enabled locator, I already provided an --security-properties-file, once I am connected, I don't need to provide this option again when I am doing "status locator --name", it should use the same connection properties to do the tcp connection operation needed by the "status locator" command.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)