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

Trouble using kerberos with new sarama version using new asn1 lib #1526

Closed
TheMacies opened this issue Oct 30, 2019 · 1 comment
Closed

Trouble using kerberos with new sarama version using new asn1 lib #1526

TheMacies opened this issue Oct 30, 2019 · 1 comment
Labels
stale Issues and pull requests without any recent activity

Comments

@TheMacies
Copy link

TheMacies commented Oct 30, 2019

Versions
Sarama Kafka Go
1.24 2.0.1 1.13
Configuration
  config := sarama.NewConfig()
    config.Version = sarama.V2_0_0_0

    config.Net.SASL.Enable = true
    config.Net.SASL.Mechanism = sarama.SASLTypeGSSAPI

    config.Net.SASL.GSSAPI = sarama.GSSAPIConfig{
      AuthType: sarama.KRB5_USER_AUTH, 
      Realm: "<realm>",
      ServiceName: "kafka",
      Username: "<username>",
      Password: "<password>",
      KerberosConfigPath: "/etc/krb5.conf",
    }
Logs

[Sarama] 2019/10/30 12:31:17 Error while performing GSSAPI Kerberos Authentication: EOF

Problem Description

We updated sarama library to handle Go 1.13 ( from version 1.23.0 to 1.24.0 ) and it seems that new version of Sarama lib breaks kerberos communication. I looked through changes in Sarama code and verified that this change breaks it. I compiled the service with the old (forked) asn1 lib and now it works fine.

Is there really no reason to use the old lib ?

Issues mentioned in the previously used library regarding asn1 are still 'open'.

golang/go#18834
golang/go#18832

@TheMacies TheMacies changed the title Trouble using kerberos with new sarama version using std ans1 Trouble using kerberos with new sarama version using new asn1 lib Oct 30, 2019
@ghost
Copy link

ghost commented Feb 21, 2020

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the master branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

@ghost ghost added the stale Issues and pull requests without any recent activity label Feb 21, 2020
@ghost ghost closed this as completed Mar 22, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and pull requests without any recent activity
Projects
None yet
Development

No branches or pull requests

1 participant