Databricks JDBC driver attempting to pass access token (JWT) from an external IDP (OKTA)

151640 — Tue, 25 Jun 2024 02:15:12 GMT

Configured a Databricks workspace for SSO to an IDP (OKTA).
Databricks JDBC driver 02.06.38.1068

Attempting to connect to Databricks using a URL similar to following where access token is obtained from the IDP (OKTA). Using tool such as SQLSquirrel with the driver fails.

jdbc:databricks://dbc-xxxx-yyyy.cloud.databricks.com:443/default;transportMode=http;ssl=1;AuthMech=11;Auth_Flow=0;httpPath=/sql/1.0/endpoints/9xxxxxxx59;Auth_AccessToken=token-here;

[Databricks][JDBCDriver](500593) Communication link failure. Failed to connect to server. Reason: HTTP Response code: 400, Error message: Authorization related error response returned, but no token expired message received.
java.sql.SQLException: [Databricks][JDBCDriver](500593) Communication link failure. Failed to connect to server. Reason: HTTP Response code: 400, Error message: Authorization related error response returned, but no token expired message received.
at com.databricks.client.hivecommon.api.HS2Client.handleTTransportException(Unknown Source)
at com.databricks.client.spark.jdbc.DownloadableFetchClient.handleTTransportException(Unknown Source)
at com.databricks.client.hivecommon.api.HS2Client.openSession(Unknown Source)

Re: Databricks JDBC driver attempting to pass access token (JWT) from an external IDP (OKTA)

151640 — Thu, 27 Jun 2024 14:36:44 GMT

Yes, latest version 02.06.38.1068

Would like to know if other persons have successfully passed access tokens from an external IDP via the driver.

topic Databricks JDBC driver attempting to pass access token (JWT) from an external IDP (OKTA) in Get Started Discussions

Databricks JDBC driver attempting to pass access token (JWT) from an external IDP (OKTA)

Re: Databricks JDBC driver attempting to pass access token (JWT) from an external IDP (OKTA)