sql

liebs 2023-03-28T21:21:47.379219Z

I'm getting The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12] when trying to connect to a MSSQL DB with next.jdbc. Can I use :jvm-opts or something to set my TLS version? Doesn't look like there's a supported key in the db-spec, is that right?

seancorfield 2023-03-29T01:17:18.469559Z

You'd have to look at the SQL Server docs to see what it needs to resolve that. If it's a connection string parameter, it can go in db-spec; if it's a JVM parameter, you'll need :jvm-opts (in an alias; or -D on the java command-line or -J-D on the clojure command-line).

seancorfield 2023-03-29T01:18:45.781819Z

TLS 1.0 has been deprecated for ages and was removed from Java 11 I think. This is an old SQL Server instance?

liebs 2023-03-29T01:19:51.758599Z

I'm now away from my work computer but I ended up using jdbc-uri (not knowing I could create my own keys in db-spec, that is) and added the required param to the connection string. I got some error the message of which I cannot recall but the gist was that the protocol didn't exist? Something like that anyway

liebs 2023-03-29T01:20:02.347869Z

Probably means what you say, that I can't use TLS 1

liebs 2023-03-29T01:20:45.605259Z

The SQLServer Java driver supports Windows Authentication tho, probably gonna set that up tmw

seancorfield 2023-03-29T01:21:10.544149Z

I believe you might be able to re-enable it on some recent JDK installs but it isn't considered secure and you don't want your JDK negotiating TLS 1.0 with arbitrary servers out there...

👍🏻 1
liebs 2023-03-29T01:22:25.802429Z

Legacy systems sigh