Fix: JWT token auth in Airflow 3 beta as JWT mechanism changed #47835
+19
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
provider:edge
kaxil
approved these changes
Mar 17, 2025
vincbeck
approved these changes
Mar 17, 2025
tyrellcurry
pushed a commit
to tyrellcurry/airflow
that referenced
this pull request
Mar 21, 2025
agupta01
pushed a commit
to agupta01/airflow
that referenced
this pull request
Mar 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unfortunately I needed to notice that the recent changes in JWT token generation/validation broke the Edge Worker API calls in main. Just a small adjustment needed which even reduces a diff between 2.10 and 3.0 line.
This also (again) triggers me that I need to find time to add a Edge Worker test into CI...
How to test?
breeze start-airflow --python 3.12 --load-example-dags --backend postgres --executor EdgeExecutor --answer yand see that EdgeWorker comes-up and reports no task. Before this PR on main it failed authentication and got a 403 error.