Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/kafka] Fix scram class name for KafkaClient in JAAS #42425

Closed
wants to merge 1 commit into from
Closed

[bitnami/kafka] Fix scram class name for KafkaClient in JAAS #42425

wants to merge 1 commit into from

Conversation

Rablet
Copy link
Contributor

@Rablet Rablet commented Jul 26, 2023

Description of the change

The kafka_jaas.conf file generated when SASL is enabled contains the following KafkaClient information:

KafkaClient {
   org.apache.kafka.common.security.plain.ScramLoginModule required
   username="myuser"
   password="mypassword";
   };

Using this to connect to a cluster results in the following error:
No LoginModule found for org.apache.kafka.common.security.plain.ScramLoginModule

It appears there is a typo in the class name. Replacing the word 'plain' with 'scram' fixes it.

Updates the JAAS KafkaClient element when SASL is enabled from using class
org.apache.kafka.common.security.plain.ScramLoginModule
to using class
org.apache.kafka.common.security.scram.ScramLoginModule

This will allow the file to be used to connect to SASL clusters

Possible drawbacks

Unknown

Signed-off-by: Robin <hi@rablet.dev>
@github-actions github-actions bot added the kafka label Jul 26, 2023
@github-actions github-actions bot added the triage Triage is needed label Jul 26, 2023
@javsalgar javsalgar added the verify Execute verification workflow for these changes label Jul 26, 2023
@github-actions github-actions bot added in-progress and removed triage Triage is needed labels Jul 26, 2023
@bitnami-bot bitnami-bot removed the request for review from javsalgar July 26, 2023 12:07
@andresbono
Copy link
Contributor

Thank you for submitting this PR! Once merged, the fix will be available in the next release of the containers.

@andresbono
Copy link
Contributor

Hi, we made some major changes in the bitnami/kafka container and those changes should fix this issue already. Please pull the latest version of the container. You can find more information here: https://github.com/bitnami/containers/tree/main/bitnami/kafka#notable-changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kafka solved verify Execute verification workflow for these changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants