Exploring methods to connect to internal resources protected by self-signed SSL certificates
anyone managed to find an easy way to connect to an internal resource thats protected with a self signed ssl certificate
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.
Based on the information available in the extracts, it seems that there are some challenges when trying to connect to an internal resource protected with a self-signed SSL certificate using Airbyte. In the Airbyte documentation, it is mentioned that to set up an SSL connection, you need to use a client certificate and add it to the “SSL PEM file” field. The connector will automatically add it to the secret keystore. You can also enter your own password for the keystore, but if you don’t, the password will be generated automatically. However, in a forum post, a user reported an issue when trying to connect to a TLS enabled Amazon DocumentDB using the MongoDB source connector. The connection test failed because it was not using the Amazon RDS CA Certificate for the TLS connection that is required by Amazon DocumentDB. Another user in the same thread mentioned that most of the database connectors in Airbyte do not allow the user to set custom certificates. A workaround suggested was patching the destination ES docker image to set the trust store as expected. In a Github issue, a user reported a similar issue when trying to connect to Gitlab API with a self-signed certificate. Unfortunately, there doesn’t seem to be an easy way to connect to an internal resource protected with a self-signed SSL certificate using Airbyte based on the information available in the extracts. It might be best to follow the updates on these issues or reach out to the Airbyte community for further assistance.