You are viewing limited content. For full access, please sign in.

Question

Question

LF Discussions Support for TLS 1.2

asked on April 21, 2021 Show version history

When installing LF Discussions 10.2, I have found that it uses SQL Server 2005 Native Client (v9.00) for connection to the database. However, this version of SQL Server Native Client doesn't support TLS 1.2. With only TLS 1.2 enabled, when configuring the DB connection in DiscussionsConfig, I get the following error:

 

Message: System.Data.Odbc.OdbcException (0x80131937): ERROR [08001] [Microsoft][SQL Native Client]Encryption not supported on the client. ERROR [08001] [Microsoft][SQL Native Client]SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm

 

If I enable TLS 1.0 on the Discussions Server and SQL Server, it works without issue (now that it has a matching and supported protocol), but it is not recommended to enable this version of TLS.

I tried to manually install the SQL Server 2012 Native Client (v11.4) and uninstall the v9.00 SQLNCLI, then I get the following error when configuring the database in DiscussionsConfig:

 

Message: System.Data.Odbc.OdbcException (0x80131937): ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

 

So my determination is, that LF Discussions 10.2 wants to use SQLNCLI 9.00, and if you remove it, it doesn't know what to use.

 

Has anyone found a way to tell Discussions to use the newer SQLNCLI (possibly something in the config files to change)?

 

If you reinstall LF Discussions, the SQLNCLI 9.00 installs with it, as part of the prerequisites. In a nutshell, this means that the current version of LF Discussions does not support TLS 1.2 (as it requires a SQLNCLI that doesn't support TLS 1.2). Currently, the only workaround I've found is enabling TLS 1.0 and sticking with the SQLNCLI 9.00, which is not desirable.

 

Anyone have thoughts or a similar experience?

0 0

Replies

replied on June 6, 2021

Hallo,

Did you receive a response regarding this issue? We have the exact same issue.

Thanx

0 0
replied on September 15, 2022

Hello, I am also wondering about this issue. Has anyone heard back?

 

 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.