dbconnect unable to make unecrypted connection

[PeaceHealthDan]

On Splunk Enterprise 9.2 and  DBConnect 3.17.2

I'm in the process of replacing our old Splunk instance, and with the new version of DBConnect, I seem to be unable to disable SSL ecryption on connection to the database.

It's a Microsoft MS-SQL database. I connect using the generic MS SQL driver. I do not have "Enable SSL" checked, I have encrypt=false in the jdbc URL:

jdbc:sqlserver://phmcmdb01:1433;databaseName=CM_PHE;selectMethod=cursor;encrypt=false

and yet, it cannot connect, throwing the 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: SQL Server did not return a response. 

The old system running DBConnect 3.1.4 on Splunk Enterprise 7.3.2 can connect just fine without ssl enabled. 

Why is DBConnect insisting on attempting an SSL connection? The SQL server is obviously not requiring it, or the old server would not work. Or is this a false error message and diverting me from some other problem?

[PickleRick]

It's not about DBConnect itself. It's about JDBC, becaus that's what's responsible for the actual connection. See https://learn.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties

There is an interesting paragraph in authentication parameter description which might pertain to you.

[hwrdthdck]

It's a shame that people reply but don't offer any real help. Telling anyone to look at the specs does not help if you took the time to read the problem

[PickleRick]

Did you actually read the docs? Especially those for the JDBC module?

[Meett]

Hello @PeaceHealthDan @aavyu20 , Can you try to add "trustServerCertificate=true" parameter to your JDBC URL and check how it goes? If that doesn’t work try to use MS-SQL Server using MS Generic Driver & MS Generic Driver with Windows Authentication

[aavyu20]

@PeaceHealthDan 
Unforturnate to find no replies to your query. I too have similar issue with DBConnect app version (3.18.0).

Did you find a solution to your problem? or still persists?