-
Notifications
You must be signed in to change notification settings - Fork 53
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
Support for brod_gssapi and other custom brod sasl authenticators #82
Comments
From source code 'brod_client.ex':
I can try to make a PR adding the validation needed for the callback related tuple to that function but don't know if you expect any other problems down the stream. |
A PR is welcome. We can either stop validating it or validate this additional value. Both approaches are fine! |
We're also looking to have this option as part of Broadway Kafka. Just curious @ramonpin - which SASL mechanism are you trying to support? |
@aravindanck our intention is to have support for the SASL_PLAINTEXT with GSSAPI at least. We probably will need to make several consecutive PRs to other erlang/kafka's ecosystem proyects used by this module. |
@ramonpin Is there a PR for this one already? If not, are you planning to raise one soon? |
Sorry guys some problems in other areas of the application leave me no time for this. @aravindanck great work from your side. Where you able to make it work with brod_gssapi library? Hoping to contribute soon. |
@ramonpin It should work for brod_gssapi library, as the validation check enables you to work with any SASL callback module. I tried this with a callback module built for a different SASL mechanism |
As stated in the documentation the BroadwayKafka.Producer module is able to pass any configuration on the client_config option down to the :brod.start_client/3.
Right now the code contains a validation that restricts the sasl configuration options to the values:
But :brod also supports using authentication plugins as:
For example you can use GSSAPI auth with kerberos by using the brod_gssapi plugin and the following client configuration:
Are you considering to allow this functionality?
The text was updated successfully, but these errors were encountered: