-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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/schema-registry] SASL_SSL is not working #70483
Comments
Thank you for bringing this issue to our attention. Since it seems you are familiar with the cause of the error, would you like to create a PR to implement a solution? The Bitnami team will be excited to review your submission and offer feedback. You can find the contributing guidelines here. Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance. |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/schema-registry
What architecture are you using?
None
What steps will reproduce the bug?
What is the expected behavior?
This configuration has been tested with
confluentic
docker image and it works.keystore
is not needed forSASL_SSL
What do you see instead?
keystore
is requiredAdditional information
I've tested this using Kafka in AWS MSK
The text was updated successfully, but these errors were encountered: