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

Community

Other: Automatic approval of TLS certificates

Arushi Sinha User

Hi Product team,

Hope this feature request finds you well and it also grabs your attention.

We have been facing this issue where all our connectors break due to inability to connect with the SQL database (Destination in our case).

This happens when there are any changes made to the server or when they are restarted as part of maintenance. 

In this case, we have to manually reconnect each destination and then the connector via - 'Test Connection' and 'Confirm' TLS Certificate > Save.

This manual process is very tedious and also leads to downtime.

We were wondering if we could please have the TLS Certificate automatically  approved to prevent disruption in syncs for the connectors ? - I believe this will help other customers too. 

Kind Regards

Arushi

Please sign in to leave a comment.

Comments

6 comments

Date Votes
  • Official comment
    Pieter Humphrey Fivetranner
    • Edited

    Hi everyone, 
    Please respond with which database(s) you are experiencing this with, and whether it is a connector or a destination.

  • Meenachi S User

    Hi Everyone,


    I'm also facing same issue connection broken due to TLS certification. Is there any way to automatic?

  • Derek Byrne User

    This auto approval ability would certainly help. I'm having the same issue due to Monthly reboots of the servers.

    The timing is also as issue as it happens overnight.

     

  • Josh Rodgers User

    This needs to be implemented. Our connections break monthly due to server reboots.

  • Niraj Fivetranner

    Kaiser Aluminum runs into this issue also

  • Pieter Humphrey Fivetranner
    • Edited

    We looked into this and it may be possible to eliminate the underlying issue.  The root cause might be that SQL Server generates a fresh self-signed cert on every restart because no stable certificate is installed. Consider deploying a persistent TLS certificate (CA-signed or a stable self-signed one) on your SQL Server instances, this would eliminate the problem entirely — no security tradeoff required. SQL Server's fallback self-signed certificate is ephemeral — it's generated fresh each time the SQL Server service starts, which means the thumbprint changes on every restart, triggering Fivetran's revalidation requirement.

    1. The primary how-to guide — start here:

    Encrypt connections to SQL Server by importing a certificate

    This is the main step-by-step: install a certificate into the Windows cert store, grant the SQL Server service account read access to the private key, then select it in SQL Server Configuration Manager. Two steps: configure the cert, then configure encryption settings.

    1. Certificate requirements — what the cert must look like:

    Certificate requirements for SQL Server

    Covers the specific requirements a cert must meet (must be in local computer cert store, must use AT_KEYEXCHANGE KeySpec, SAN must include all hostnames clients use to connect, etc.). Important for customers trying to generate their own cert and hitting silent failures.

    1. Certificate management via SQL Server Configuration Manager (SQL 2019+):

    Certificate management (SQL Server Configuration Manager)

    For SQL Server 2019 and later, certificate management is integrated directly into SQL Server Configuration Manager, which simplifies importing and deploying certs across failover cluster instances and availability groups. If Q2 is on SQL 2019+, this is the easier path than the manual MMC/registry approach.