emredjan commented on issue #55147: URL: https://github.com/apache/airflow/issues/55147#issuecomment-3270735965
> But if you feel like you have still problems with it and airflow **should** provide other mechanisms - feel absolutely free. You can roll your sleeves and contribute it - and become one of the ~3500 people who not only used Airflow for absolutely free (without any guarantes if you read the licence) but also contributed back when they saw there is a neeed. Apologies for sounding entitled, it wasn't my intention, as I'm grateful what Airflow provided for us. I will definitely try to look into this and try to contribute if I can find the source of my issue, and hopefully make it easier to use it environments with strict security restrictions (like financial corporate settings). >I believ others solved it by configuring the certificates to be exactly those that webserver uses - support for it was added in this PR and apparently it's been released in 3.0.4 https://github.com/apache/airflow/pull/53574 I saw this change, but I believe that's what broke my configuration, as it was somewhat working on 3.0.3 (albeit patchy), but completely stopped when I upgraded to 3.0.4. I will dig further. Thanks for the suggestions @potiuk -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
