-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Kerberos : switch MIT to Heimdal #26438
Comments
I changed the issue type from bug to "feature" - because that is what it is. Why don't you implement this kind of switch @Jeoffreybauvin ? It does not seem to be a difficult one to implement, requires little Python knowledge and you could test it with your Heimdal Kerberos, so you seem to be a very good candidate to implement, test and contribiute - you could join the > 2100 contributors to Airflow - mostly users like you who had some problem and solved it by contributing. I also marked it as "good-first-issue", so maybe someone will pick it but, the "surest" way to get it in is if you implement it (just wanted you to know so that you know that such features only get implemented if someone gets interested in implementing it, and you seem to be rather interested in implementing it). |
I can try, but I'm not sure what I need to do. Change the possible options for kinit ? Or switch to heimdal ? |
Add options only. Removing support for MIT kerberos would make a breaking change (and there are probably plenty of users using MIT one, so that wouldn't be empathetic towards them. |
can you please assign it to me , |
Assigned @maheshsv ! |
Apache Airflow version
2.3.4
What happened
Hi,
In my infrastructure, we are using Kerberos Heimdal for our keytabs. I can see that airflow seems to be using MIT...
I managed to switch to Heimdal by customizing the image : replacing krb5 packages with heimdal-clients.
But the kinit command used by Airflow seems to be specific with MIT :
the "-r 5m" seems to be the problem. Adding --renewable or deleting -r 5m seems to fix this issue. But how to "fix" this properly ?
Regards,
What you think should happen instead
Either :
How to reproduce
Use kerberos with Heimdal.
Operating System
Debian (Docker)
Versions of Apache Airflow Providers
Deployment
Other Docker-based deployment
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: