Summary
The user is facing an SSL certificate verification error when using the connector-builder and wants to know if it’s possible to disable it.
Question
Hi!,
When I use the connector-builder (from UI) and send my request to the url, the response is this:
HTTPSConnectionPool(host='---my_host---', port=---my_port---): Max retries exceeded with url: ---my_url--- (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1129)'))) -
The problem is due to SSL certificate verification. I need to disable it. Is it possible?
Thanks in advance
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.
Join the conversation on Slack
["disabling-ssl-certificate-verification", "connector-builder", "ssl-certificate-error"]
Based on the information provided in the extracts, it seems that Airbyte does support different SSL modes for certain connectors like Postgres and MySQL. These modes include disable, which disables encrypted communication between Airbyte and the source. However, it’s important to note that you are not permitted to disable SSL while using Airbyte Cloud. Unfortunately, the extracts do not provide specific information about disabling SSL verification for the connector-builder UI. It’s recommended to check the specific documentation for the connector you are using, as the available options may vary. If you are using a self-hosted version of Airbyte, you might be able to disable SSL by modifying the configuration of your specific connector. However, this is generally not recommended due to security reasons. It’s better to resolve the SSL certificate issue. If you continue to experience issues, it would be best to reach out to the Airbyte community or support for more specific guidance.
But in case that the connector (source) is generated using connector-builder (through api), is there possibility of disable SSL certificate verification?
Unlikely. I don’t know if you could use an http:// base URL that won’t do TLS certificates at all. But as far as I know, I did not see if we support disabling tls verification.
It’s very likely going to be easier for you to either provision valid certificates, or to do tls termination and provide insecure http api.
Thanks Natik for your answer