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

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.3.2
   
   ### What happened and how to reproduce it?
   
   Airflow 3.3.2 runs in kubernetes+istio (mutual TLS on egress). After adding 
a connection to trino with login/password via http, I get the error: "TLS/SSL 
is required for authentication. To use HTTPS, specify 'https://' in the host 
URL (which takes precedence over http_scheme), or, if the host URL has no 
scheme, pass http_scheme='https'" when I click the Test connection button.
   
   ### What you think should happen instead?
   
   It happens because trino==0.339.0 in 
https://raw.githubusercontent.com/apache/airflow/constraints-3.3.2/constraints-3.12.txt
 does not allow using "http:"  
https://github.com/trinodb/trino-python-client/blob/0.339.0/trino/dbapi.py#L221 
. You should probably switch to using the trino==0.340.0 package 
https://github.com/trinodb/trino-python-client/blob/0.340.0/trino/dbapi.py#L222 
and ensure that the parameter allow_insecure_auth: bool = True is passed. At 
the moment the workaround is to use trino==0.337.0 in constraints.txt
   
   ### Operating System
   
   Rhel 9
   
   ### Deployment
   
   Other
   
   ### Apache Airflow Provider(s)
   
   trino
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-trino 6.6.1
   
   ### Official Helm Chart version
   
   _No response_
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _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]

Reply via email to