Hi,
How can I create a profile in the SQL for Confluence app that will connect to a SQL server host that has Force Encryption enabled?
I'm using the values below,
Profile name: Force Encrypt
Data source name: none
Setup type: By connection string
Connection string: jdbc:jtds:sqlserver://server1:1433/database1?ssl=true
Driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver JAR location: confluence/WEB-INF/lib/mssql-jdbc-12.8.1.jre11.jar
~~~~~~~
Error message received is "I/O Error: DB server closed connection"
Opened a Microsoft support case,
Discovered I needed to update our Data Source Profile's connection string to use the FQDN of the SQL server that has enforce encryption enabled.
The registered secure certificate on our SQL server is also using the FQDN.
Yet, with enforce encryption disabled, the Data Source Profile does not need the FQDN. Go Figure?!
Another possible Connection string to use on a SQL Server forcing client connection encryption,
jdbc:jtds:sqlserver://yoursqlserver:1433/yourdatabase;TrustServerCertificate=True;
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This document may help. https://confluence.atlassian.com/confkb/cannot-connect-confluence-to-ms-sql-server-using-force-encryption-591594220.html
It comes down to modifying the start parameters for Confluence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Shawn Doyle - ReleaseTEAM ,
initially, I was going to reply I already tried the recommended resolution, below, in that doc, but, our Data Source profiles are still unable to connect to that SQL server.
jdbc:jtds:sqlserver://YourConfluenceServer:1433/YourConfluenceDatabase?ssl=true
Yet, there appears to be other recommendations in that doc that I will explore.
Sorry, if that was not clear earlier.
Also, opened a support ticket with Appfire, the vendor for SQL for Confluence (Pro Edition), which we are using to create our SQL Data Source profiles.
Also, was able to create a new Data Source profile that can connect to another SQL Server that has forced encryption enabled. The SQL servers, upon a quick review, found
Data Source profile can connect to SQL 2019 Enterprise on Windows 2022 standard with forced encryption enabled.
Data Source profile can not connect to SQL 2019 Standard on Windows 2019 standard with forced encryption enabled.
Thank You!
Alfredo Lagrosa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.