-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Airflow LDAP search returned multiple results #15720
Comments
Note : |
Older constraints/images of Airflow 2.0.2 had this problem, but this have been fixed since (it was a problem with Flask Application Builder and it was fixed in 3.2.3 version of FAB. Not sure how you installed Airflow but you might need to pull latest 2.0.2 image of Airlfow or manually upgrade to latest FAB==3.2.3. Please see the discussion in (seemingly unrelated) issue: #15451 (comment) Current version of constraints for Airflow 2.0.2 already contains the fixed FAB version (https://github.com/apache/airflow/blob/constraints-2.0.2/constraints-3.8.txt#L5) In Airflow 2.0.3 (in a few days) this will be the default (3.2.3+ for FAB will be in the original constraints). |
@potiuk Thanks for the reply, i used the bitnami docker image : |
Yeah - they still use FAB 3.2.2 (just checked). I think you have few options :)
|
We use the Bitnami Helm chart to deploy on our private cloud. |
BTW. I think we will skip 2.0.3 and go stratight to 2.1 stay tuned! |
Apache Airflow version: 2.0.2
Kubernetes version (if you are using kubernetes) (use
kubectl version
): 1.15.5Environment: Private Cloud (Rancher)
uname -a
): linuxWhat happened:
What you expected to happen:
No ERROR , successful login
How to reproduce it:
Have LDAP and try to connect to Airflow with LDAP user's credentials
Anything else we need to know:
webconfig :
From here
The text was updated successfully, but these errors were encountered: