Provision to Microsoft SQL Server
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure Akamai Connection
- Configure AWS Connection
- Configure Azure Key Vault Connection
-
- Workload Identity Federation Authentication
- Workload Identity Federation - Azure Identity Provider Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Workload Identity Federation Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Supported OIDC Claims
-
-
-
- Working with the Built-in CA
- Add AWS Public CA
- Add AWS Private CA
- Add DigiCert One Certificate Authority
- Add Entrust
- Add GlobalSign Atlas
- Add GlobalSign MSSL
- Add GoDaddy
- Add Google Cloud Private CA
- Add a HID PKIaaS CA
- Add Certificate Manager - Self-Hosted
- Set Up an OpenSSL Certificate Authority Connector
- Create a Sectigo Certificate Manager Certificate Authority
- Add Zero Touch PKI
- Set Up Certificate Expiration Notifications
- Using a Custom DNS Provider
-
-
-
-
- Create an F5 BIG-IP LTM Machine
- Create a Microsoft Azure Private Key Vault Machine
- Create a Microsoft Azure Application Registration Machine
- Create a Microsoft IIS Machine
- Create a Microsoft Windows (PowerShell) Machine
- Create a Microsoft SQL Server Machine
- Create a Common KeyStore Machine
- Create a Citrix ADC Machine
- Create an Imperva WAF Machine
- Create a VMware NSX Advanced Load Balancer (AVI) Machine
- Create an A10 Thunder ADC Machine
- Create a Cloudflare Machine
- Create Kemp Virtual LoadMaster Machine
- Create a Palo Alto Panorama Machine
- Create a Radware Alteon Machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
- Provision Certificates to Radware Alteon
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing Certificate Lifecycle Settings
- Reissuing Certificates in Next-Gen Trust Security
- Downloading Certificates, Certificate Chains, and Keystores
- Retiring, Recovering, and Deleting Certificates
- Finding Certificates in the Certificate Inventory
- Importing Certificates from a CA Using EJBCA
- Domain-Based Validation for External Emails
-
- Create a Workload Identity Management or Discovery Agent Built-in Account
- Create an OCI Registry Built-in Account
- Create a Certificate Manager - Self-Hosted Built-in Account
- Create a Scanafi Built-in Account
- Toggling a Built-in Account on or Off
- Editing Built-in Accounts
- Deleting Existing Built-in Accounts
- Renew Existing Built-in Accounts
- Troubleshooting
Provision to Microsoft SQL Server
Use this procedure to provision a certificate from Next-Gen Trust Security to a Microsoft SQL Server machine.
Tip: Before you begin, verify that the Microsoft SQL Server machine is already created in Next-Gen Trust Security and that prerequisite configuration is complete. See Create a new Microsoft SQL Server machine.
- Sign in to Next-Gen Trust Security.
- Click Insights > Machines.
- Select the Microsoft SQL Server machine you want to provision a certificate to.
- Click Provision a certificate.
- From Choose a certificate from the inventory, search for and select the certificate you want to provision.Verify that you selected the correct certificate by reviewing the Subject DN, Validity, and Fingerprint.
- From CAPI Store, select the certificate store where the certificate will be installed.
- Enter a Friendly Name. This name is how the certificate appears when used by SQL Server.
- (Optional) Enable Allow private key to be exported if the private key must be exportable.
- (Optional) To provision the certificate to the SQL Server instance, enable Installation Endpoint.Note: When enabled, Next-Gen Trust Security installs the certificate in the Windows certificate store and applies it to the SQL Server instance. If disabled, the certificate is installed only in the Windows certificate store.
- In SQL Server Instance, specify one of the following:
- Leave empty to default to localhost.
- Enter COMPUTERNAME to apply the certificate to all SQL Server instances.
- Enter COMPUTERNAME\INSTANCE to target a specific SQL Server instance.
- (Optional) Enable Restart the SQL Server instance to restart the instance automatically after provisioning.
- (Optional) To create the certificate record without pushing it, set Push upon saving to No.When set to Yes (default), saving installs the certificate. If Installation Endpoint is enabled, the certificate is also applied to SQL Server.
- Click Save.
After saving, Next-Gen Trust Security installs the certificate and creates an installation record on the Installations tab.