Repository navigation
Conversation
This branch has not been deployed
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.
#30 added SASL support. Currently, in order to configure SASL plain, I think the best practice for kafdrop would be to configure the appropriate login module in the sasl.jaas.config property in kafka.properties. Something like...
This unfortunately puts user/pw information in plaintext in a file when running directly from a JAR.
Due to the nature of SpringBoot configuration, the change in this PR has the side effect of enabling configuration of the user/pw in the environment (
kafka_saslJaasConfig) and through a command line argument (--kafka.saslJaasConfig) as is currently supported for brokers (kafka_brokerConnect/--kafka.brokerConnect).