kyungjunleeme commented on PR #53597: URL: https://github.com/apache/airflow/pull/53597#issuecomment-3105119117
## Reflections on the Feedback and Purpose of the PR After receiving the feedback yesterday, I spent some time reflecting on Airflow's philosophy and current internal structure. It helped me understand the intention behind the feedback more clearly. From my perspective, there seems to be a distinction between the authentication mechanisms used for user-facing APIs and those used internally between components within Airflow. The reason I created this PR was to improve the developer experience for users interacting with the Airflow API through Swagger UI, making it easier to test and trigger endpoints directly. During this process, I noticed that a 422 Unprocessable Entity error was occurring when using application/x-www-form-urlencoded content type. To address this, I made a small change to support form-based input without modifying Airflow’s core structure or authentication logic. The goal was to make the authentication endpoint more user-friendly, especially for those exploring the API via tools like Swagger. While working on this, I also observed that JWT token handling in Airflow is not yet fully unified across different parts of the system. I believe this presents an opportunity to submit a follow-up PR that would refactor and unify the token handling logic, ensuring consistency and paving the way for smoother integration of OAuth2.0 and SSO in the future. --- (Note: I drafted my thoughts and structure in Korean first, based on my understanding of the feedback and the current state of the codebase. ChatGPT helped only with polishing the English writing and markdown formatting — all technical reasoning and intent came from my own review.) If there's anything I may have misunderstood, I’d really appreciate your clarification. @ashb -- 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]
