[AMBARI-22718] Allow security.inter.broker.protocol: SASL_SSL for all stack versions #88
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.
What changes were proposed in this pull request?
This change removes the minimum stack version requirement for
SASL_SSL
in Kafka.8fce2a1 added support for
security.inter.broker.protocol: SASL_SSL
in Ambari, but only for stacks with theKAFKA_EXTENDED_SASL_SUPPORT
flag. It turned out that the flag is for other SASL features (eg. SASL/SCRAM, etc.), and Kafka supportsSASL_SSL
in earlier versions, too.This eliminates the need to manually tweak
stack_features.json
.How was this patch tested?
Installed kerberized HDP 2.4, 2.5 and 2.6 clusters via blueprints. Verified that Kafka Brokers in all of these versions work fine with
security.inter.broker.protocol: SASL_SSL
.Existing unit tests pass: