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
- Building an AI-Forward Healthcare Organization on Data and Governance Databricks Blog ·
- Databricks Accelerates Agentic Media Buying with New Reference Implementation Databricks Blog ·
- NBCUniversal Migrates to Databricks Lakehouse for Scalable Analytics Databricks Blog ·
- Databricks SDK for Python v0.123.0: API changes and breaking updates Databricks Python SDK Releases ·
- Databricks Go SDK v0.167.0 Adds Cloud Provider Auth Fields Databricks Go SDK Releases ·
- Databricks SDK Java v0.138.0 Adds Model Provider Config Fields Databricks Java SDK Releases ·