Skip to main content

Community

Allow TrustServerCertificate=True bypass for SQL Server Connector.

Answered

Please sign in to leave a comment.

Comments

1 comment

  • Official comment

    Hi Tarun,

    Thank you for raising this request and for sharing the SQL Server connection properties example.

    If I understand correctly, you're looking for an option similar to Encrypt=True; TrustServerCertificate=True, where encrypted communication is still enforced while bypassing strict certificate chain validation.

    Today, we do not support this behavior in the SQL Server connector because disabling certificate validation increases the risk of man-in-the-middle (MITM) attacks. That said, I understand there are environments where customers rely on self-signed certificates or internal PKI setups and need a more flexible configuration option.

    I'd love to better understand the specific setup and constraints on your side, including how broadly this impacts your deployments and whether there are alternative certificate management options available to your team. That context would help us evaluate the request more effectively internally.

    If you're open to it, please feel free to book 30 minutes on my calendar, and we can discuss further.

    Thank you again for the feedback

    Best, 
    Rean Rodrigues - Fivetran Product Team