topic Re: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_conn in Get Started Discussions

[Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_connect:

Sathya_7 — Fri, 30 Jan 2026 16:23:34 GMT

Hi everyone,

I’m trying to create an ODBC connection to Databricks using the Simba ODBC driver
and I’m getting the following error when testing the connection:

FAILED!
[Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection:
SSL_connect: error code: 0

Environment:
- OS: Windows
- Simba ODBC Driver version: 2.07.07.1016
- Databricks workspace: AWS
- Authentication: SSO
- ThriftTransport: HTTP
- SSL: enabled

Re: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_conn

pradeep_singh — Sun, 01 Feb 2026 05:22:58 GMT

Use the latest Simba ODBC with ThriftTransport=HTTP and correct HTTP Path, switch SSO to OAuth U2M (AuthMech=11, Auth_Flow=2)

Re: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_conn

szymon_dybczak — Sun, 01 Feb 2026 10:19:52 GMT

Hi @Sathya_7 ,

The authentication flow you're trying to use (SSO) is not supported. Below you can find all supported authentication methods:

If you'd like to authenticate using OAuth user-to-machine (U2M) or OAuth 2.0 browser-based authentication, add the following configurations to your ODBC compute settings and any special or advanced driver capability settings:

For detailed steps refer to docs:

Authentication settings for the Databricks ODBC Driver (Simba) | Databricks on AWS

Re: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_conn

Sathya_7 — Mon, 02 Feb 2026 08:25:21 GMT

Hi everyone,

Sorry for the confusion in my earlier message — I mistakenly mentioned SSO.

To clarify, the authentication method I’m actually using is Username and Password.

Re: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_conn

szymon_dybczak — Mon, 02 Feb 2026 11:14:06 GMT

Hi @Sathya_7,

Ok, that explains everything. Basic authentication using username and password reached end of life in July 10, 2024. Use U2M or M2M authentication flow instead.

At below link you will find description how to properly authenticate using U2M or M2M flow:

Authentication settings for the Databricks ODBC Driver (Simba) | Databricks on AWS