fionawhim commented on issue #48798: URL: https://github.com/apache/airflow/issues/48798#issuecomment-4215909501
> This issue has been resolved by [#59245](https://github.com/apache/airflow/pull/59245). Feel free to re-open the issue if you think the issue is still there Reading over these issues I’m not sure that #59245 fixes this… my understanding of this issue is for Airflow DAGs using the HttpOperator and friends to connect to external APIs that use OAuth / OIDC authentication. The resolution mentioned above seems to add flexibility in how other services would authenticate to the Airflow API, which seems like it’s the opposite direction from this issue. Forgive me if I’m mis-reading, though. (FWIW I found this issue trying to sus out Airflow’s OIDC support… I was hoping for a pattern like in GitHub Actions where a workflow can call a function that is essentially “give me an OIDC token that identifies me!” and then use that to authenticate to an external API. In GitHub’s case the token describes the repo, branch, and environment being run in. In Airflow’s I would imagine some combination of connection ID and DAG name.) -- 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]
