You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to modify the public function db_connect( $allow_bail = true ) function in wp-includes/wp-db.php to allow php to connect to my SQL Server using a non-CA-trusted certificate.
I added the ODBC Connection parameter for TrustServerCertificate to be true, instead of the default false.
Problem now is, any new updates from the ProjectNami github project will reset the change. It would be great to have a setting for that in the wp-config.php file, or something along those lines to ensure that updates don't clobber the connection parameters.
The text was updated successfully, but these errors were encountered:
While it wouldn't prevent any non-encrypted connectivity, having the option to only connect via trusted certificates is probably important for some folks. For me, having the TrustServerCertificate setting defaulted to true would be fine.
I had to modify the
public function db_connect( $allow_bail = true )
function inwp-includes/wp-db.php
to allow php to connect to my SQL Server using a non-CA-trusted certificate.I changed the following lines:
to
I added the ODBC Connection parameter for
TrustServerCertificate
to betrue
, instead of the defaultfalse
.Problem now is, any new updates from the ProjectNami github project will reset the change. It would be great to have a setting for that in the
wp-config.php
file, or something along those lines to ensure that updates don't clobber the connection parameters.The text was updated successfully, but these errors were encountered: