TLS version handshake issue about databricks-sql-python

[sander-goos]

Hi, could you please check the openssl version on the VM?
E.g.: python -c "import ssl; print(ssl.OPENSSL_VERSION)". The TLS version used by the handshake is determined by the openssl library. The client should use the highest version it supports in the Client Hello message, so it is odd that it is trying with TLSv1 while clearly it also has TLSv1.3 available.

[waynetheron]

Hi, could you please check the openssl version on the VM? E.g.: python -c "import ssl; print(ssl.OPENSSL_VERSION)". The TLS version used by the handshake is determined by the openssl library. The client should use the highest version it supports in the Client Hello message, so it is odd that it is trying with TLSv1 while clearly it also has TLSv1.3 available.

HI

It prints

OpenSSL 1.1.1n 15 Mar 2022

What is interesting is this is the same python modules that run perfectly fine on another system (copied the entire python folder to this Azure VM) so it does seem to be an underlying OS-related issue but the weird thing is why does it sometimes try 1.3 (this bit has me stumped as it is not consistent). I have counted the intervals between success and failure and there is no pattern there either. It can fail 11 times in a row before using 1.3 and working, other times it can fail 16 times before working. When it works it tends to work the next run again but then starts to fail after that.