Open shahmanash opened 2 months ago
Thank you for contacting us. We'll get back to you.
Just add ;encrypt=false
to your database name (thus in the field "Database"), so it becomes
Ring;encrypt=false
Thanks,
I can confirm that the suggested fix of adding the ;trustServerCertificate=true
or ;encrypt=false
to the value in the Database field works.
But it might not be the most elegant way to solve the issue.
Yes, it seems it works as a workaround right now. We'll make a fix to address it properly
Connection to a remote MSSQL server from an IPT running in docker fails with SSL related error, see attached screenshot.
The testing (temporary) fix is to add
trustServerCertificate=true;
to the JDBC url definition in the jdbc.properties file i.e. Change https://github.com/gbif/ipt/blob/master/src/main/resources/jdbc.properties#L25mssql.url=jdbc:sqlserver://{host};databaseName={database}
tomssql.url=jdbc:sqlserver://{host};databaseName={database};trustServerCertificate=true;
However it is not persistant in a docker container and probably not the best way in a prod environment.
Please advise on the best possible way to address the issue.