RDSC-3561 Add custom keystore and truststore for the jedis client in redis sink #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces additional configuration options for specifying custom keystore/truststore for the jedis client in redis sink. This allows the client to use different keys and certificates than the default ones passed to the JVM.
This change updates the Jedis client to version 6.0.0. and takes advantage of the newly introduced SSL options.
The options are applied only if
redis.ssl.enabled
is true.Configuration properties for each new SSL options:
redis.ssl.truststore.path
: Specifies the path to the truststore file used for SSL.redis.ssl.truststore.password
: Specifies the password for the truststore file.redis.ssl.truststore.type
: Specifies the type of the truststore (e.g., JKS, PKCS12) (default: JKS).redis.ssl.keystore.path
: Specifies the path to the keystore file used for SSL.redis.ssl.keystore.password
: Specifies the password for the keystore file.redis.ssl.keystore.type
: Specifies the type of the keystore (e.g., JKS, PKCS12) (default: JKS).see https://redislabs.atlassian.net/browse/RDSC-3561