You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: