Skip to content

HydroBaseDMI - handle certificate requirements for JDBC 13.2.1 driver #53

@smalers

Description

@smalers

I was fixing a bug where stored procedures could not be properly handled in the ReadTableFromDataStore command. Previously I had updated TSTool to Java 11. ChatGPT said that Java 11 was not compatible with older JDBC driver for what I was trying to do. So, I updated the JDBC driver to 12.2.1, which is compatible with Java 11 and newer. Then I got a database connection error related to not having a valid certificate. In this case, I am doing software development on one machine and using HydroBase on another (so I don't have to waste time installing the database on multiple machines). I resolved by adding the trustServerCertificate=true string to the database connection string. It also appears that encrypt=true is the default behavior, which may trigger using the certificate?

The bottom line is that I have it working but I'd like to get the State's opinion on the connection string parameters.

  • should encryption be on (the default if not otherwise specified)
  • is it OK to hard-code to trust the certificate (because there is no certificate)

Given that HydroBase is used in read-only mode, it seems like the above is OK. Such things are probably going to show up more and more related to security.

Metadata

Metadata

Assignees

Labels

highPriority: next release if possiblequestion

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions