Why does DBeaver fail to validate a PostgreSQL server's SSL certificate when the hostname resolves via DNS, and how can I configure a custom truststore to fix it?
When connecting to a PostgreSQL instance over TLS using DBeaver, the client sometimes rejects the server's certificate despite the certificate being valid and trusted by the system Java keystore. The issue appears to be related to DNS resolution of the host name used in the connection string, which may cause a mismatch between the certificate's subject alter
dbeaver