[
https://issues.apache.org/jira/browse/GEODE-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Godwin updated GEODE-9420:
-------------------------------
Description:
Unexpected behavior observed around autloading `gfsecurity.properties`
during`gfsh connect`:
When specifying `ssl-keystore`, `ssl-truststore`, and their relative password
properties in a `gfsecurity.properties` file, but other `ssl-*` properties in
`gemfire.properties` or as system properties, `gfsh connect` does not complete
successfully.
Adding `ssl-enabled-components` to the `gfsecurity.properties` file allows the
autoloading to work during connect and the command does complete successfully.
However, the value of `ssl-enabled-components` is redacted in the logs and we
would like to avoid this result.
Also, specifying `security-properties-file` allows us to connect (i.e. `gfsh
connect --security-properties-file=gfsecurity.properties`), though we would
like the convenience of autoloading.
Acceptance:
* Autoloading of `gfsecurity.properties` works, regardless of which properties
are specified in the file.
was:
Unexpected behavior observed around autloading `gfsecurity.properties`
during`gfsh connect`:
When specifying `ssl-keystore`, `ssl-truststore`, and their relative password
properties in a `gfsecurity.properties` file, but other `ssl-*` properties in
`gemfire.properties` or as system properties, `gfsh connect` does not complete
successfully.
Adding `ssl-enabled-components` to the `gfsecurity.properties` file allows the
autoloading to work during connect and the command does complete successfully.
However, the value of `ssl-enabled-components` is redacted in the logs and we
would like to avoid this result.
Also, specifying `security-properties-file` allows us to connect (i.e. `gfsh
connect --security-properties-file=gfsecurity.properties`), though we would
like the convenience of autoloading.
> GFSH connect will not autoload gfsecurity.properties without
> ssl-enabled-components defined
> -------------------------------------------------------------------------------------------
>
> Key: GEODE-9420
> URL: https://issues.apache.org/jira/browse/GEODE-9420
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Affects Versions: 1.15.0
> Reporter: Ivan Godwin
> Priority: Minor
>
> Unexpected behavior observed around autloading `gfsecurity.properties`
> during`gfsh connect`:
> When specifying `ssl-keystore`, `ssl-truststore`, and their relative password
> properties in a `gfsecurity.properties` file, but other `ssl-*` properties in
> `gemfire.properties` or as system properties, `gfsh connect` does not
> complete successfully.
> Adding `ssl-enabled-components` to the `gfsecurity.properties` file allows
> the autoloading to work during connect and the command does complete
> successfully. However, the value of `ssl-enabled-components` is redacted in
> the logs and we would like to avoid this result.
> Also, specifying `security-properties-file` allows us to connect (i.e. `gfsh
> connect --security-properties-file=gfsecurity.properties`), though we would
> like the convenience of autoloading.
>
> Acceptance:
> * Autoloading of `gfsecurity.properties` works, regardless of which
> properties are specified in the file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
