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

Lack of Support for OAuthBearer Mechanism with SASL_PLAINTEXT Protocol in Klaw #2550

Open
rkyadav271098 opened this issue Aug 12, 2024 · 1 comment
Labels
Backend Backend tasks

Comments

@rkyadav271098
Copy link

What is currently missing?

Klaw currently lacks support for the OAuthBearer mechanism with the SASL_PLAINTEXT protocol for Kafka. Specifically, the sasl.login.callback.handler.class property, which is required to configure the OAuthBearer mechanism, is not currently configurable within Klaw. This limitation prevents users from successfully connecting to Kafka clusters that utilize OAuthBearer authentication.

How could this be improved?

To address this issue, Klaw should be updated to include support for the OAuthBearer mechanism by allowing the configuration of the sasl.login.callback.handler.class property. This enhancement would enable users to authenticate with Kafka clusters using OAuthBearer and the SASL_PLAINTEXT protocol.

Is this a feature you would work on yourself?

Yes, I am interested in working on this feature. I have already tested the necessary changes locally and am prepared to contribute these updates to the open-source project.

@muralibasani
Copy link
Contributor

@rkyadav271098 very impressive that you have raised this issue and already have a working version of it.

Indeed, OAuthBearer mechanism is not supported in klaw., I assume it's relatively a minor change in klaw cluster api to handle the new mechanism.

Pls submit a pr whenever you are ready.

@muralibasani muralibasani added the Backend Backend tasks label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend Backend tasks
Projects
None yet
Development

No branches or pull requests

2 participants