mik-laj commented on issue #8111: URL: https://github.com/apache/airflow/issues/8111#issuecomment-660906974
> Do you think there is value in allowing different auth rules on a view-by-view basis? If so, parts of my design support this. Do you mean authorizations/permission control? We have a separate issue about it: https://github.com/apache/airflow/issues/8112 I haven't thought about this topic in detail yet. This week, I'd like to do that. I will probably want to do everything as Ash suggested. > It seems like Airflow would benefit from having a few prebuilt backends with common authentication schemes (Bearer Token, JWT, basic auth, etc.) What do you think about me implementing a few of those? It is beyond the scope of the current work. Personally, I will try to ensure integrations with CAS (e.g. [KeyCloak](https://www.keycloak.org/)) that will allow us to authenticate using various methods in a much more secure way e.g. it provides 2FA. If we prepare [documentation](https://github.com/apache/airflow/issues/8123), each organization will be able to easily prepare an authentication backend in accordance with the requirements of its organization. If you are willing to implement the implementation, I will be happy to help with the review. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
