Skip to content

Fix azure u2m#882

Merged
samikshya-db merged 2 commits into
databricks:mainfrom
samikshya-db:samikshya-chand_data/u2mWorking
Jul 8, 2025
Merged

Fix azure u2m#882
samikshya-db merged 2 commits into
databricks:mainfrom
samikshya-db:samikshya-chand_data/u2mWorking

Conversation

@samikshya-db
Copy link
Copy Markdown
Collaborator

Description

  • The earlier client ID seems to be no longer working. Adding a short term fix on Azure U2M resolution.

Testing

  • Tested using example :
"jdbc:databricks://<azure workspace>:443/default;transportMode=http;ssl=1;AuthMech=11;Auth_Flow=2;TokenCachePassPhrase=test;httpPath=/sql/1.0/warehouses/<warehouseID>;";

Additional Notes to the Reviewer

  • We had shared a custom JAR with the entire U2M flow re-written on our side, customer's issues seems to be resolved then. We will wait for OAuth to get back on the RCA, but I will just change the client ID for this PR.

@samikshya-db samikshya-db merged commit d7d24da into databricks:main Jul 8, 2025
9 of 12 checks passed
@samikshya-db samikshya-db deleted the samikshya-chand_data/u2mWorking branch July 8, 2025 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants