[GEODE-9420] GFSH connect will not autoload gfsecurity.properties without ssl-enabled-components defined

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.15.0
• Component/s: gfsh
• Assignee: Unassigned
• Reporter: Ivan Godwin
• Created: 09/Jul/21 02:04
• Updated: 09/Jul/21 18:59

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.