Databricks Java SDK v0.116.0: Optional Client ID in OAuth
Databricks Java SDK v0.116.0 allows the client ID to be optional in OAuth token acquisition. This fix prevents NullPointerExceptions for users authenticating via browser OAuth flows where the IdP JWT lacks a client ID, enabling account-wide token federation by omitting the parameter when it's absent. The change impacts developers using the Java SDK for OAuth authentication.
Fixes (1) ›
Make the client ID optional in DatabricksOAuthTokenSource. Previously getToken() threw a NullPointerException ("ClientID cannot be null") when no client ID was set, which prevented token exchange for users authenticated through a web browser OAuth flow whose IdP JWT does not contain a client ID. When the client ID is null or empty, the client_id parameter is now omitted from the token exchange request to perform account-wide token federation
https://github.com/databricks/databricks-sdk-java/releases/tag/v0.116.0
Related releases
- Databricks `ai_transcribe()` SQL Function for Audio Transcription (Beta) Databricks Release Notes ·
- Databricks Lakebase Snapshots API (Beta) for Programmatic Management Databricks Release Notes ·
- Databricks Introduces Session Restore for Serverless Jobs in Public Preview Databricks Release Notes ·
- Announcing On-Demand State Repartitioning for Apache Spark Structured Streaming on Databricks Databricks Blog ·
- Databricks Genie now displays visualizations directly in Slack replies Databricks Release Notes ·
- Databricks Introduces Configurable Data Retention for System Tables (Beta) Databricks Release Notes ·