Database Management
SSL connections from DPA to SQL Server monitored instance
This article addresses the issue where a user is unable to connect to DPA to monitor an instance that requires SSL connections.
First published date
Last published date
Overview
If DPA is unable to connect to a SQL Server instance that requires SSL connections, the resolution depends on which driver is used to connect to the instance:
- DPA 2021.3 and later can use either the jTDS driver or the Microsoft JDBC driver:
- If the instance was registered in DPA 2021.3 and later, the MS JDBC driver is used.
The following section describes how to resolve this issue for both drivers.
Product section
Cause
SSL was enabled on monitored SQL Server instances.
Resolution
Determine which driver is being used
To find out which driver is being used, open the Update DB Instance Connection Wizard:
- From the DPA menu in the upper-right corner, click Options.
- Under Monitor Setup > Database Instances, click Update Connection.
- Select the database instance, and click Next.
- On the Update Monitored Database Instance Connection Information page, look at the available properties:
- If the MS JDBC driver is used, the SSL mode drop-down menu is shown:
- If the jTDS driver is used, the SSL mode drop-down menu is not shown, but the Microsoft JDBC Driver option is there to allow you to change drivers:
- If the MS JDBC driver is used, the SSL mode drop-down menu is shown:
If the Microsoft JDBC driver is used
On the Update Monitored Database Instance Connection Information page, select the appropriate SSL mode option, depending on how restrictive the settings are for SSL on your server. The options (from least to most secure) are:
- Disable
- No certificate validation
- Validate server certificate
- Validate server certificate and match hostname
Note: If the ForceEncryption flag is set to Yes on the SQL Server database instance, all communication with the instance must be encrypted. Do not choose Disable as the SSL mode.
If the jTDS driver is used
On the Update Monitored Database Instance Connection Information page, update the connection information to get DPA to request the SSL connection. In the JDBC URL Properties, and add the following:
ssl=request
If there are other entries in this field, you can add this with a semicolon as a separator. For example:
NTLMv2=true;ssl=request.
If this does not resolve the issue, enter the following property instead:
ssl=require
If the DPA repository server requires SSL connections
If SQL Server instance that holds the DPA repository database uses the jTDS driver and the instance is changed to require SSL connections, then a similar flag needs to be added to the file that is has the DPA database connection string. This is the repo.properties file.- Open the repo.properties file in a text editor. The file is in the following location:
<DPA_home>/iwc/tomcat/ignite_config/idc/repo.properties - Add one of the following, depending on how restrictive the settings are for SSL on your server:
- repo.jdbcDriverProperties=useSSL\=request
- repo.jdbcDriverProperties=useSSL\=require
- Save the file.
- Restart DPA.
Bulk update
- If you have multiple DPA instances and many SQL Server instances monitored with each DPA repository then you can execute the following SQL statement on the DPA repository database(s):
UPDATE COND SET CONN_ADD_PROPS = 'useNTLMv2=true;ssl=request' where DB_TYPE = 'SQL Server'; UPDATE COND SET CONN_URL_PROPS = 'useNTLMv2=true;ssl=request' where DB_TYPE = 'SQL Server';
- Restart DPA.
Scripts are not supported under any SolarWinds support program or service. Scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.