Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

updating a new mssql driver in the admin doesn't preserve trust arguments

Description

see linked task for details

Environment

None

Attachments

7

Activity

Show:

Pothys - MitrahSoft 20 June 2023 at 15:31

yes, the error was only occurred for the above combination.

Michael Offner 20 June 2023 at 15:06

i was wrong above, yes that is exactly when we expect it, you only get it in that combination?

Pothys - MitrahSoft 20 June 2023 at 13:21
Edited

Checked this issue with latest MSSQL driver version . when set the TrustServerCertificate = false and encrypt = true, it throws the error "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption" in the admin datasource page.

Michael Offner 20 June 2023 at 10:25

what is your setting for “encrypt“ and “trustServerCertificate“ in the detail view.

we expect this error when “enyrypt“ is set to true and “trustServerCertificate“ as well. Please set one of them to false and try again.

Pothys - MitrahSoft 19 June 2023 at 07:01

Checked this issue with newest version of the MSSQL driver. Now when trying to edit an datasource and changed the TrustServerCertificate = false, I don't get the error "The property trustServerCertificate does not contain a valid boolean value. Only true or false can be used". But it throws the error "The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption" in the admin datasource page.

Fixed

Details

Assignee

Reporter

Priority

Labels

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Parent

Sprint

Created 9 June 2023 at 13:44
Updated 21 June 2023 at 08:48
Resolved 20 June 2023 at 15:56