KAFKA-20440: Use default Keystore type instead of hardcoding PKCS12 keystore type#22041
Open
scholzj wants to merge 1 commit intoapache:trunkfrom
Open
Conversation
…eystore type Signed-off-by: Jakub Scholz <www@scholzj.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR should fix
KAFKA-20440. It
removes the hardcoded PKCS12 in-memory keystore type that is used when
users use PEM certificates with Kafka brokers or clients. And it
replaces it with the default Keystore type based on the Java Virtual
Machine configuration. That should make the PEM support more flexible
and make it work even when running Kafka clients or servers in
environments with disabled PKCS12 support (such as the Chainguard
FIPS-compliant Java images that are based on Bouncy Castle and do not
support PKCS12 stores).