Configuring Secured Trino with Superset #16123
-
A clear and concise description of what the bug is. Expected resultsConnection Successful Actual results[SupersetError(message="HTTPSConnectionPool(host='myhost', port=443): Max retries exceeded with url: /v1/statement (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1091)')))", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Trino', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})] ScreenshotsIf applicable, add screenshots to help explain your problem. How to reproduce the bugTry to connect to secured trino over https EnvironmentOpenshift kubernetes ChecklistMake sure to follow these steps before submitting your issue - thank you!
Additional contextHow to add SSL related information and JKS truststore to authenticate trino from superset |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
hi,did you solve this problem? i wanna connect trino use https,but fail |
Beta Was this translation helpful? Give feedback.
-
Working Solution: Use certificate in connection string |
Beta Was this translation helpful? Give feedback.
Working Solution: Use certificate in connection string
trino://{UserName}:{Password}@{trino url without https}:443/{catalog name}?verify={ca certificate path on superset host}
e.g. below
trino://sbagal:XXXXX@trino-dev.apps.co:443/my_catalog?verify=/etc/cert/mycert.ca