Microsoft SQL Server
Copy link to the page “Microsoft SQL Server”Binds the certificate to a SQL Server instance and gives the service account access to the key.
What happens
- The service agent on the server fetches the task from the appliance over outbound HTTPS, port 443.
- The integration imports the certificate into the Windows certificate store.
- 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.
- Verification: the integration reads the instance's certificate and tests an encrypted connection.
Technical details
- Connection
- The integration runs through the service agent on the server. The service agent connects over outbound HTTPS to the appliance, port 443 by default. You open no port into the server.
- Service ports
- 1433, 1434
- What you need
- The service agent installed on the server. The service 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
- Integrations
-
windows-sql1.3.0 - Note
-
- SQL Server on Windows requires RSA 2048, 3072 or 4096 bits with a legacy CSP, machine key and KeySpec 1 (AT_KEYEXCHANGE). ECC and CNG are refused before key permissions, the instance registry binding or services change. The integration also checks that the certificate and private key match. Microsoft: https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/certificate-requirements