-
Notifications
You must be signed in to change notification settings - Fork 251
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
Improve the support of gssapi/sasl, fully realize wraptoken. #460
Comments
@jcmturner I think you should make unwrap more compatiable, like java implements: Line 132 in 663478b
java implements: https://github.com/openjdk/jdk/blob/jdk-11+0/src/java.security.jgss/share/classes/sun/security/jgss/krb5/Krb5Context.java#L1051 |
I am also having this issues |
set the following lines in
|
I've made some progress on the issue --> https://github.com/MikhailMS/gokrb5 - if anyone wants to check it against their Kafka, would be appreciated If I can keep up the pace, then soon it would be offered as PR - so it would be up to owner to include it into the next release whenever that happens :) |
@MikhailMS I also have similar problems. So, can this PR solve your problem? Thanks!
|
Now, wrapToken.go only supports Wrap Tokens v2 defined in
https://datatracker.ietf.org/doc/html/rfc4121#section-4.2.6
The Kerberos Version 5 GSS-API Mechanism: Version 2
for Backwards Compatibility Considerations, is should implement Wrap Tokens v1 defined in rfc1964
see https://datatracker.ietf.org/doc/html/rfc4121#section-6 for backword compatibility
see https://datatracker.ietf.org/doc/html/rfc1964#section-1.2.2 for old format
Now, if we encounter kerberos which use rc4, errors will happen like that:
2022/03/16 18:36:59 failed to init session context while performing kerberos authentication, err: wrong Token ID. Expected 0504, was 6030
2022/03/16 18:36:59 failed to authorize with kerberos, err: wrong Token ID. Expected 0504, was 6030, zookeeper server: kb01.sa:2181
2022/03/16 18:36:59 error in resending auth creds: wrong Token ID. Expected 0504, was 6030
The text was updated successfully, but these errors were encountered: