Error when install framwork on SQL db

[beolafsen]

Tried to install Oqtane on a SQL server. Have done that on the same sql server before - but now I got this error:
(OK installation on LocaleDB)

A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an untrusted entity

[sbwalker]

Microsoft seems to have introduced some breaking changes in .NET 6 related to enabling encryption by default for SQL Server. I was unable to install Oqtane on LocalDB on .NET 6 until I added Encrypt=false to the connection string. Here is a related thread:

dotnet/SqlClient#1312

It appears there is a new version of SqlClient available v4.0.0-preview3.21293.2 - perhaps this will resolve the issue.

[sbwalker]

Oqtane has been upgraded to latest SqlClient v4.0.0-preview3.21293.2 - please try again.

[sbwalker]

On Aug 25, 2021 Microsoft included this item in the release notes for Microsoft.Data.SqlClient 4.0.0-preview1.21237.2:

"Encrypt default value set to true

The default value of the Encrypt connection setting has been changed from false to true. With the growing use of cloud databases and the need to ensure those connections are secure, it's time for this backwards-compatibility-breaking change."

Currently Oqtane does not provide an explicit value for encryption in the connection string - which means it now defaults to true on .NET 6 and if your database server is not configured to support encryption it will likely result in errors. I believe the solution is to add an option to the SQL Server configuration component so that the user can specify if they wish to use encryption. This option would not be required for LocalDB as it does not support encryption.

[sbwalker]

problem should now be resolved - get the latest code and try an installation on SQL Server and specify False for the new Encryption option that was added to the installation UI.

[beolafsen]

It works fine now'

[sbwalker]

Microsoft recommended also adding a SQL Server config option for Trust Server Certificate - which is described here:

https://docs.microsoft.com/en-us/sql/relational-databases/native-client/features/using-encryption-without-validation?view=sql-server-ver15

So I will add this as well.