Skip to content

← All integrations

Windows · Application and database

Binds the certificate to a SQL Server instance and gives the service account access to the key.

The service agent on the server fetches the task from the appliance over outbound HTTPS on port 443 and installs the certificate locally on the server. The appliance never connects to the server.

What happens

  1. The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
  2. The package imports the certificate into the Windows certificate store.
  3. The certificate is bound to the instance, the service account gets access to the key and the instance is restarted. If it fails: Rollback puts the previous certificate back and restarts the instance.
  4. Verification: the package reads the instance's certificate and tests an encrypted connection.

Technical details

Connection
The package runs through the service agent on the server. The agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
Service ports
1433, 1434
You need
The service agent installed on the server. The agent on the SQL Server host itself, with local administrator rights. Verification signs in to the local instance with Windows authentication.
Platform
SQL Server 2012 and later, Windows Server 2012 R2 and later
Actions
Discovery, Installation, Verification, Rollback
Packages
windows-sql

Get started