docs: Document Databricks U2M (User-to-Machine) OAuth authentication#1680
Merged
Conversation
Fixes #1661 Adds a third authentication section for the Databricks connector covering U2M OAuth — triggered by supplying only databricks_client_id without databricks_token or databricks_client_secret. Notes the deferred (on-trigger) initialization and that Spark Connect mode does not support U2M. Verified against spiceai/spiceai trunk (crates/data-connectors/connector-databricks/src/lib.rs).
✅ Pull with Spice PassedPassing checks:
|
|
🚀 deployed to https://494f0cb3.spiceai-org-website.pages.dev |
|
🚀 deployed to https://2b4b778e.spiceai-org-website.pages.dev |
lukekim
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Fixes #1661
Adds documentation for the Databricks connector's third authentication method — User-to-Machine (U2M) OAuth — which is triggered when only
databricks_client_idis supplied (withoutdatabricks_tokenordatabricks_client_secret).Changes
website/docs/components/data-connectors/databricks/index.mdOnTrigger) initialization, and the Spark Connect mode limitation.databricks_client_idanddatabricks_client_secretso the M2M-vs-U2M distinction is clear at a glance.Reference
Verified against
spiceai/spiceaiatorigin/trunk:crates/data-connectors/connector-databricks/src/lib.rs—build_auth_credentialsselectsAuthCredentials::U2Mwhen onlyclient_idis set;ComponentInitialization::OnTriggerfor U2M; the Spark Connect path does not implement U2M and usesdefault()initialization.Test plan
cd website && npm run buildpasses locallywebsite/docs/only (per skill rule for new content)