geonetwork / geonetwork/docker-geonetwork
GEONETWORK_DB_CONNECTION_PROPERTIES for SQL Server
- Dominant language
- Shell
- Stars
- 40
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
It seems that the property GEONETWORK_DB_CONNECTION_PROPERTIES is not used when using SQL server as the database. We added "encrypt=true;trustServerCertificate=true" to GEONETWORK_DB_CONNECTION_PROPERTIES but according to the logs it still tries to connect with "trustServerCertificate=false"
```
2024-04-04T11:41:43,255 WARN [geonetwork.databasemigration] - - Migration: Exception running migration for version: 4.4.3-0 subversion: SNAPSHOT. Cannot create PoolableConnectionFactory ("encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:5726bea6-77a8-4256-ba88-69a1833ef109)
```
I'm not a Java developer by any means but shouldn't `jdbc.connectionProperties` also be referenced in sqlserver.xml?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.