cklat commented on issue #51362: URL: https://github.com/apache/airflow/issues/51362#issuecomment-3598306966
> > > Auth backends have been deprecated in Airflow 3, sadly there is no other alternative. What is your custom API authentication rely on? Which authN/authZ service are you using? > > > > > > Hey [@vincbeck](https://github.com/vincbeck) > > internally we are using keycloak but we need to have it for any OIDC provider. > > If auth_backend is deprecated for airflow 3, so be it but is there any option to keep this kind of auth process in airflow 3 as well? What options are there as for right now for airflow 3? > > Or is this a total breaking change for airflow 2 user's that have been using auth_backends and cannot migrate to airflow 3 at all? > > I understand the frustration, let me look into it and think about a solution. I might have something in mind. In the meantime, can you share your configuration? What I mean by that: > We'd really like to test out/migrate airflow 3 because it gives us some features that we could benefit from, therefore thanks for your effort, really appreciate that! As for your questions: > * Which auth backend are you using? > * What is your authentication configuration? I guess you're using OAUTH? Not sure if I'm completely following but let me know if something may be still unclear or insufficient. We are using the same auth backend that @andre-s-pedrosa-alb posted with his `user_auth.py`. It's basically the exact same code. We then reference the `user_auth.py` in the [api] section of the airflow.cfg as per the docs which I posted in the link above. For authentification we are using OAUTH (OAUTH2), correct! -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
