Add Token Federation Support for Databricks SQL Python Driver #691
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Description
This PR implements token federation functionality for the databricks-sql-python driver, enabling seamless integration with external Identity Providers (IdPs) like Azure AD, Okta, and others.
Token federation allows users to authenticate with external IdPs and automatically exchange those tokens for Databricks in-house tokens when needed. This enables:
Flow:
How is this tested?
Extensive testing was performed covering:
- External service principal tokens from Azure AD
- Automatic token exchange with Databricks workspace
- Authentication as service principal in Databricks
- Browser-based OAuth flow with automatic token handling
- Pre-obtained user tokens from external IdPs
- Authentication as actual users in Databricks
- Token caching with proper expiry handling
- Automatic refresh when tokens expire
- Graceful fallback when exchange fails
- Tested with GCP Databricks workspace using Azure AD tokens
- Tested with Azure Databricks workspace
- Verified issuer-based exchange decision logic
Related Tickets & Documents