Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-03-10 Thread via GitHub


pierrejeambrun commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-4031299114

   Review done 


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-03-06 Thread via GitHub


Abhishekmishra2808 commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-4012695765

   @pierrejeambrun I have been working on this issue for a while and its 
waiting for your 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-03-06 Thread via GitHub


pierrejeambrun commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-4012385875

   We do not assign issues to people as per our recent change of policy. Please 
feel free to work on it and directly contribute a PR @jaymasiwal 


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-03-05 Thread via GitHub


jaymasiwal commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-4007670972

   Hi, I would like to work on this issue.
   
   I previously contributed to Apache Airflow with PR #61609 and would like to 
help improve the UI error handling here.
   
   I'll start by reproducing the issue locally and updating the UI to show a 
clearer permission error message for 403 responses.


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-03-02 Thread via GitHub


potiuk commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-3986405172

   @Abhishekmishra2808 We are unassigning you from this issue as part of our 
updated [assignment 
policy](https://github.com/apache/airflow/blob/main/contributing-docs/04_how_to_contribute.rst#contribute-code-changes).
   
   This is not meant to discourage your contribution — quite the opposite! You 
are still very welcome to work on this issue and submit a PR for it. Simply 
comment that you are working on it and open a PR when ready.
   
   We found that formal assignments were not working well, as they often 
prevented others from contributing when the assignee was not actively working 
on the issue.


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-07 Thread via GitHub


jscheffl commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-3864677960

   No need to ping individual contributors - we are on reviews regularly. More 
messages make life rather painful.


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-07 Thread via GitHub


Abhishekmishra2808 commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-3864389660

   Hey @jscheffl , 
   For now, I’ve implemented a cleaner user message when permissions are 
insufficient. 
   Hiding the trigger button based on viewer permissions is definitely a better 
long-term approach - I plan to work on that after this PR is merged, since it 
requires additional changes and testing.
   


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-05 Thread via GitHub


jscheffl commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-385541

   Can we also make it possible to hide the trigger button if only viewer 
permissions? Or can this be only detected post-trigger attempt?


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-05 Thread via GitHub


pierrejeambrun commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-3852581780

   Sounds good, you're assigned


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



Re: [I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-04 Thread via GitHub


Abhishekmishra2808 commented on issue #61460:
URL: https://github.com/apache/airflow/issues/61460#issuecomment-3851449876

   Hi @pierrejeambrun @chobberoni , 
   I’d like to work on this issue.
   
   From my understanding, the problem occurs when users with restricted roles 
receive a generic 403 error without clear permission feedback in the UI. I plan 
to improve how permission-related failures are handled and displayed.
   
   **Plan:**
   1. Reproduce the issue locally using a DAG Viewer role.
   2. Identify where 403 responses are handled in DAG trigger/history UI flows.
   3. Add explicit handling to show a clear permission message.
   4. Add tests to validate unauthorized scenarios.
   5. Verify consistency across similar UI actions.
   
   Please let me know if this approach looks good - I’d be happy to proceed.
   


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



[I] When a DAG Viewer tries to trigger a DAG, the action fails with 403 [airflow]

2026-02-04 Thread via GitHub


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

   ### Apache Airflow version
   
   3.1.7
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When a DAG Viewer tries to trigger a DAG, the action fails with 403, and the 
Home → View History also shows 403 without clearly indicating it’s an 
authorization issue.
   From a user experience perspective, it might be clearer if 
permission-related failures explicitly mention insufficient permissions / role 
restrictions
   
   ### What you think should happen instead?
   
   it might be clearer if permission-related failures explicitly mention 
insufficient permissions / role restrictions
   
   ### How to reproduce
   
   Testing during DAG level roles implementation on the Astronomer Astro client 
-- requires internal Astro access
   
   ### Operating System
   
   macOS sequoia 15.7.3
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### 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]