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

Sathya_7
New Contributor II

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

 

pradeep_singh
Honored Contributor III

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

Thank You
Pradeep Singh - https://www.linkedin.com/in/dbxdev

szymon_dybczak
Esteemed Contributor III

Hi @Sathya_7 ,

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

szymon_dybczak_0-1769940993132.png

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:

szymon_dybczak_1-1769941168190.png

For detailed steps refer to docs:

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

 

Sathya_7
New Contributor II

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. 

szymon_dybczak
Esteemed Contributor III

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.

szymon_dybczak_0-1770030753901.png

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

View solution in original post