Database connection is invalid setup for MSSQL 2016 - Splunk DBconnect

[gabo]

Hi,

I am trying to connect to Microsoft SQL Server 2016 Standard Edition (64‑bit) using Splunk DB Connect 4.1.1 with the Splunk DBX Add‑on for Microsoft SQL Server JDBC 1.3.2. My environment is running Java OpenJDK 17.

I have already tried disabling Java security policies, and I also tested different combinations of the connection string properties ( encript and TrustServerCertificate ). However, none of these changes worked.
The connection still fails with the following error:

When attempting the connection, I receive the following error:

The property "encrypt" is set to "true" and the property "trustServerCertificate" is set to "true", but the driver was unable to establish a secure connection to SQL Server using Secure Sockets Layer (SSL) encryption: Error: Certificates do not conform to algorithm constraints. ClientConnectionId: cfdc7e4a-068a-42f4-a134-1d02332d99d0

Regards!

[PrewinThomas]

@gabo 

Java 17 enforces stricter TLS/SSL algorithm constraints than older Java versions. Also your Microsoft JDBC driver 1.3.2 is very old which may not support this.

So try upgrade the JDBC Driver and test it or downgrade your java to 11 and test

Regards,
Prewin
🌟If this answer helped you, please consider marking it as the solution or giving a Karma. Thanks!

[victor_menezes]

Hi @gabo,

While configuring your connection, just add the parameter "trustServerCertificate" as false and "encrypt" as false in the connection properties by clicking in that "Add properties" button instead of managing the JDBC URL directly, for example:

Or disable the enable ssl flag and set those properties to false.

The error is because of a combination of those flags that are written by default by the driver, but anything you add there as properties in the connection will take precedence.

[computermathguy]

We are getting the same error on all our MSSQL connections except one. I've used DBConnect for many years (since 2016) and never came across this issue.  Started happening after upgrading DBConnect to 4.1.1 and Red Hat to version 8.

P.S. I thought trustServerCertificate=true was the correct property setting to resolve this certificate error?

[gabo]

Hi @victor_menezes ,

Thank you for your response.

We applied the suggested configuration, setting the "encrypt" property to "false" and the "trustServerCertificate" property to "false". However, we are still getting the following error:

"encrypt" property is set to "false" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: Certificates do not conform to algorithm constraints. ClientConnectionId:97ed09b1-9506-43c0-8bea-f2473c1e04b8

 Regards!

[computermathguy]

A few weeks ago we upgraded to DBConnect 4.1.1.  We can connect to one MSSQL host but not the others

Same error:

"encrypt" property is set to "true" and "trustServerCertificate" property is set to "true" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: Certificates do not conform to algorithm constraints. ClientConnectionId:a3859b49-32ea-4200-b83a-2d083b41ba59