GitHub user potiuk added a comment to the discussion: Airflow API authentication using Kerberos is not working from the version 2.8.0
I think I'd recommend you to upgrade to much newer version of airflow. Upgrading to 2.8.0 (or any .0) makes very little sense in general, because almost by definition it has bugs (All the bugs - and only bugs) that were fixed in 2.8.1, 2.8.2, 2.8.3 and 2.8.4 - and since there were some teething problems with migration to Auth Managers in 2.8.0, it's very likely you are hitting those bugs that were fixed in one of the later versions of 2.8.* So first thing first. Upgrade to latest patchlevel of newer version of airflow (ideally latest patchlevel of 2.10 - that's always my recommendation to upgrade to latest version). Then - I think you should open an issue if it does not work for you - there were some changes in how configuration of APIs are recommended, so I recommend to read the appropriate docs and check if your configuration is properly done. For example Kerberos auth is now part of the FAB provider and ideally you should update your documentation to follow that https://airflow.apache.org/docs/apache-airflow-providers-fab/stable/auth-manager/api-authentication.html This is all described in release notes - so you can also read those - between the version you started from and migrated to. Once you check it all and upgrade and update the configuration if you find things not working, open an issue please with some details - there shoud be some log indicating errors in case you see the authentication not working - and people who will look at the issue need to know all the details to be able to help you. BTW: > airflow https://airflow-test.xxxx.com/api/experimental/pools is an experimental API that is going to be removed in Airflow 3, so you should rather investigate the authentication issues you have with the REST API GitHub link: https://github.com/apache/airflow/discussions/39683#discussioncomment-11090401 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
