yzhangyext opened a new issue, #55275:
URL: https://github.com/apache/airflow/issues/55275

   ### Apache Airflow version
   
   3.0.6
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Similar to this past issue: https://github.com/apache/airflow/issues/36832
   When opening the url of a specific Airflow DAG (like <my airflow 
host>/dags/<dag_id>), the user is redirected to the login page if he's not 
logged in.
   However, when the login is performed, the homepage of the webserver is 
shown, instead of the URL that was initially opened
   
   ### What you think should happen instead?
   
   It should direct to the same page from the url after login.
   
   ### How to reproduce
   
   1. Enter into Airflow and copy the URL of a specific DAG (i.e <my 
host>/dags/<dag_id>).
   2. Log out
   3. Paste the URL you copied -> you'll be redirected to the login page.
   4. Login
   5. See how you'll be redirected to the home page.
   
   ### Operating System
   
   Docker image
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-fab == 2.4.0
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   It appears a fix was done in https://github.com/apache/airflow/pull/37904
   But there seems to be a regression after Fab version 2.0.0: 
https://github.com/apache/airflow/blob/providers-fab/2.0.0/providers/fab/src/airflow/providers/fab/auth_manager/fab_auth_manager.py#L476
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to