Replies: 2 comments 2 replies
-
|
This is correct behaviour. In the new FAB, when you are connected via Oauth, you should manage your users via Oauth and mapping Oauth Groups to Roles of Airflow not via Admin of Airlfow- See FAB documentation (Airlfow really exposes FAB functionality for that part so you should ask your questions there.) https://flask-appbuilder.readthedocs.io/en/latest/security.html |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Any news so far on this? How can we create service users that only require a password then? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Apache Airflow version
2.1.3
Operating System
AWS K8s
Versions of Apache Airflow Providers
Deployment
Other 3rd-party Helm chart
Deployment details
the web pod installs extrapiplibrary
we have standard deployment on k8s and we have webconfig
What happened
We are using
CustomUserOAuthModelViewand under roles, there are only three permission that can be addcan read on CustomUserOAuthModelView, can edit on CustomUserOAuthModelView, can delete on CustomUserOAuthModelViewThe

add userbutton isnt available for Admins and the/Users/addendpoint isn't accessible by Admins.What you expected to happen
Admin roles should have access to
/Users/addendpoint and theadd userbutton should be visibleHow to reproduce
upgrade from v1.10.15 to v2.1.3
Anything else
No response
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions