Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Destination Improvement: Using a self-signed certificate for communication with the Destinations (Databricks)

Answered
Yuta Ide User

In configurations using the Hybrid Deployment, if an internal proxy exists on the network route from the Agent to Databricks and SSL communication is terminated by the internal proxy, a certificate error occurs due to the internal proxy's self-signed certificate, and test connection is failed. Therefore, we request that the Hybrid Agent also allow adding trusted certificates via the "trusted_root_ca_certs" field for communication with the Destinations (Databricks).

Best regards,

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Amanda Wong User

    Hi Yuta,



    This is a valuable request. We have added this to our backlog for feature improvements to the Hybrid Agent, specifically supporting self-signed certificates through the trusted_root_ca_certs field for Databricks connections. To help us better understand your requirements, could you provide more detail on your proxy setup and any specific pain points you've encountered with certificate validation in your environment? Any additional insight into the scale or frequency of these issues would be helpful.



    We will keep this thread updated with any progress.



    Thanks,

    Amanda

  • Kevin Kim Fivetranner

    Hi Yuta,

    I believe this capability is already supported, you are able to use a self-signed certifcate for Databricks when using Hybrid Deployment.

    Please reference this docs article for a description of the feature: https://fivetran.com/docs/deployment-models/hybrid-deployment/troubleshooting/custom-certificate-for-hybrid-deployment

    Please let me know if there are any other questions you may have!